• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 1
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      A visual way to see which features are 'Must Have', 'Should Have', 'Could Have' or 'Won't Have' following the MoSCoW format used when prioritising stories

      A toggle viewable, draggable bar to segregate your stories into prioritised blocks. Zero, one or more of the bars could be present

      Mocked up screenshot attached

          Form Name

            [JSWSERVER-8753] add MoSCoW lines to Scrum planning boards

            Can epics have fields for prioritization? like must have , should have, could have..

            Reshma Nankani added a comment - Can epics have fields for prioritization? like must have , should have, could have..

            Luca Alessi added a comment - https://www.garethjmsaunders.co.uk/2019/12/03/how-to-create-new-moscow-prioritisation-statuses-in-jira/ Could help?

            Any update on this request?

            Elie Shamey added a comment - Any update on this request?

            Personally i'd prefer it to be columns instead of rows. But I'd love to see this feature either way, for backlog prioritization!

            Remco van Grinsven added a comment - Personally i'd prefer it to be columns instead of rows. But I'd love to see this feature either way, for backlog prioritization!

            Silence for 2 years.

            Could someone from Atlassian update us on the status of this?

            Robert Rodrigues added a comment - Silence for 2 years. Could someone from Atlassian update us on the status of this?

            I also would like to see a solution to this problem that enables us to MoSCoW a sprint.

            Andrew Currie added a comment - I also would like to see a solution to this problem that enables us to MoSCoW a sprint.

            Agree with something that enables us to attribute a MoSCoW priority to a Jira issue. Colour coding would also help (or an icon). Would be especially useful for product and sprint/timebox prioritisation and deprioritisation where the originators of the Jira are not necessarily present at the decision-making point of 'what's in and what's not' mid-sprint/mid-timebox

            Julie Daniel added a comment - Agree with something that enables us to attribute a MoSCoW priority to a Jira issue. Colour coding would also help (or an icon). Would be especially useful for product and sprint/timebox prioritisation and deprioritisation where the originators of the Jira are not necessarily present at the decision-making point of 'what's in and what's not' mid-sprint/mid-timebox

            Has this feature been implemented or is it planned to be implemented in the future? It would be really useful.

            Ennio Lepri added a comment - Has this feature been implemented or is it planned to be implemented in the future? It would be really useful.

            Anything?

            Paul Snedden added a comment - Anything?

            Is there any update on this as it would be very useful?

            Kind regards,

            Rebecca

            Rebecca Gerrard added a comment - Is there any update on this as it would be very useful? Kind regards, Rebecca

              Unassigned Unassigned
              389dc871ba5a Roger Moore
              Votes:
              69 Vote for this issue
              Watchers:
              38 Start watching this issue

                Created:
                Updated: