You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I want to move section in the structure tree, I cannot move it. I can cut and copy a section into a section as a sub-section, but not reorganize the top level sections. We cannot sunset the legacy site until this is possible.
Impact
Please include hard deadlines, if the exhibit is part of an event, the issue is stopping work, etc.
Priority recommendation
asap
within the next 3 weeks
PO will prioritize - talk with Trey
Sudden Priority Justification
Required if "asap" or "within the next 3 weeks" is checked. Add "Sudden Priority" and "Maintenance/Research" labels
Expected behaviour
Actual behaviour
Steps to reproduce behaviour
Screenshots
The text was updated successfully, but these errors were encountered:
One proposed solution is to create two new options in the "Actions" menu (along with corresponding keyboard shortcuts) for moving items up and down in their current containers. This would be the simplest and most Accessible approach to meet the use case needs.
Proposed keyboard shortcuts to move an item up or down are Shift+Ctrl UpArrow and Shift+Ctrl DownArrow.
(This solution does not prevent the possibility of adding drag & drop to the Structure Pane in the future, if needed.)
Summary
When I want to move section in the structure tree, I cannot move it. I can cut and copy a section into a section as a sub-section, but not reorganize the top level sections. We cannot sunset the legacy site until this is possible.
Impact
Please include hard deadlines, if the exhibit is part of an event, the issue is stopping work, etc.
Priority recommendation
Sudden Priority Justification
Required if "asap" or "within the next 3 weeks" is checked. Add "Sudden Priority" and "Maintenance/Research" labels
Expected behaviour
Actual behaviour
Steps to reproduce behaviour
Screenshots
The text was updated successfully, but these errors were encountered: