Ability to handle Multiple UBs

[martyngigg]

This issue was originally TRAC 11277

A single crystal requirement.

Pascal Manuel at ISIS will be a good contact.

---

Keywords: SSC 2015 all SX

[martyngigg]

@NickDraper (2015-03-10T15:49:01):
Batch modify all SSC tickets to critical priority (this will also show up as an update for all those already as critical)

---

@NickDraper (2015-03-11T10:17:29):
Need to agree best way to handle this.

Options:

1. multiple peaks workspace (possibly in a PW group)
2. single PW with column for number link to UB matrix index

---

@OwenArnold (2015-03-20T15:34:46):
The decision has been made (Vates meeting 16th March 2015) that each Peaks Workspace should have a single UB and when peaks are transferred between PKWS, the they will use the UB on that workspace.

[samueljackson92]

Pascal indicated that this should still be a priority and agrees that PWs should have a single UB and when peaks are transferred they should use that UB.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you feel this is incorrect please comment to keep it alive, with a reason why.

To prevent closure, e.g. for long-term planning issues, add the "Never Stale" label.

[stale]

This issue has been closed automatically. If this still affects you please re-open this issue with a comment so we can look into resolving it.

[martyngigg]

@rosswhitfield @DannyHindson I think this is still on the SC roadmap? Is it tracked somewhere else or should we keep this on open?

[DannyHindson]

@rosswhitfield @DannyHindson I think this is still on the SC roadmap? Is it tracked somewhere else or should we keep this on open?

Yes WISH still want us to implement this so I'll reopen. I don't see another issue for this

[stale]

This issue has been automatically marked as stale because it has not had activity in 6 months. It will be closed in 7 days if no further activity occurs.
Allowing issues to close as stale helps us filter out issues which can wait for future development time. All issues closed by stale bot act like normal issues; they can be searched for, commented on or reopened at any point.
If you'd like a closed stale issue to be considered, feel free to either re-open the issue directly or contact a developer.
To extend the lifetime of an issue please comment below, it helps us see that this is still affecting you and you want it fixed in the near-future. Extending the lifetime of an issue may cause the development team to prioritise it over other issues, which may be closed as stale instead.

[stale]

This issue has been closed automatically. If this still affects you please re-open this issue with a comment or contact us so we can look into resolving it.