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
What feature or change would you like to see made?
New deploy level config: Force global segmentation panel
Why should we prioritize this feature?
Currently the segmentation panel is fixed to display current stack viewport segmentation. If switching to another active viewport with no segmentation, nothing is displayed in the segmentation panel, even if an inactive viewport does have a segmentation.
We should allow a deploy level config that enables the segmentation panel to display all segmentations regardless of active viewport. For now, this will only force display all global segmentations, new design will be required outside of scope for better UI/UX to handle scenarios where the panel needs to display conflicting segmentations.
Feat request from Flywheel meeting
The text was updated successfully, but these errors were encountered:
What feature or change would you like to see made?
New deploy level config: Force global segmentation panel
Why should we prioritize this feature?
Currently the segmentation panel is fixed to display current stack viewport segmentation. If switching to another active viewport with no segmentation, nothing is displayed in the segmentation panel, even if an inactive viewport does have a segmentation.
We should allow a deploy level config that enables the segmentation panel to display all segmentations regardless of active viewport. For now, this will only force display all global segmentations, new design will be required outside of scope for better UI/UX to handle scenarios where the panel needs to display conflicting segmentations.
Feat request from Flywheel meeting
The text was updated successfully, but these errors were encountered: