Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-11355

As the configurer of an agile board, I want to indicate which columns are "Not Started" columns and which columns are "Done" columns

    • Icon: Suggestion Suggestion
    • Resolution: Answered
    • None
    • None
    • None
    • 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.

      JIRA Agile assumes that the statuses in the left-most column equate to Not Started and the statuses in the right-most column equate to Done. A more flexible implementation would allow us to use checkboxes when configuring our boards to indicate which column(s) are Not Started columns and which column(s) are Done columns.

      For example, we use a four-step workflow for stories (Not Started->In Progress->In Review->Done). We also have the additional states of Blocked and Dropped which can be transitioned to from any state.

      I'd like to set my Scrum Board up with six columns in this order (Not Started, In Progress, In Review, Done, Blocked, Dropped). But Done and Dropped need to share the last column--otherwise we have problems closing Sprints with a mixture of done and dropped stories or sub-tasks. When Done and Dropped share the last column, there is no visual indication the story (or task) is Done or Dropped unless the details of the story (or task) are inspected. Even worse, we had to allow transition of stories to Done from any state to match the transition to Dropped from any state. Otherwise, a user might attempt to drag a story from In Progress to Done (skipping In Review) and JIRA Agile would silently put it in Dropped state (since there is no legal transition from In Progress to Done).

      On the left-side of the board, if I put Blocked to the left of Not Started, JIRA Agile counts my Not Started stories as In Progress when looking at the story point accumulation, which is incorrect.

            [JSWSERVER-11355] As the configurer of an agile board, I want to indicate which columns are "Not Started" columns and which columns are "Done" columns

            +1

            Jeff Lindsey added a comment - +1

            +1

            Dave Cavell added a comment - +1

            Tim Bodeit added a comment - - edited

            Tim Bodeit added a comment - - edited See GHS-12169

            Tim Bodeit added a comment -

            +1 On this issue. I would vote on it if I could. In my eyes, this should be reopened.

            Merging multiple Statuses in one Column (even with custom cards) and/or creating a separate boards are not sufficient workarounds.

            Tim Bodeit added a comment - +1 On this issue. I would vote on it if I could. In my eyes, this should be reopened. Merging multiple Statuses in one Column (even with custom cards) and/or creating a separate boards are not sufficient workarounds.

            rmckenrick
            A blocked state could be anywhere across the workflow, so I would recommend showing these with the Flag feature.
            https://confluence.atlassian.com/display/AGILE/Flagging+an+Issue

            I assume a dropped state would indicate that the issue will not be done in the Sprint. Would it make sense to just remove the issue from the sprint?
            https://confluence.atlassian.com/display/AGILE/Removing+an+Issue+from+a+Sprint
            Otherwise, I would suggest using a column to the right but not the last column to indicate a dropped but started issue.

            Kind regards,
            Martin
            JIRA Agile

            Martin (Inactive) added a comment - rmckenrick A blocked state could be anywhere across the workflow, so I would recommend showing these with the Flag feature. https://confluence.atlassian.com/display/AGILE/Flagging+an+Issue I assume a dropped state would indicate that the issue will not be done in the Sprint. Would it make sense to just remove the issue from the sprint? https://confluence.atlassian.com/display/AGILE/Removing+an+Issue+from+a+Sprint Otherwise, I would suggest using a column to the right but not the last column to indicate a dropped but started issue. Kind regards, Martin JIRA Agile

            Ross McKenrick added a comment - - edited

            @martin Perhaps I didn't word my suggestion clearly enough or was just too verbose. Many of our users, including me, want to put the Blocked and/or Dropped columns to the far left or far right of our boards so they don't interrupt the visualization of the standard workflow (Not Stated->In Progress->Done). Not sure how adding the status to the card or your other suggestions address this. Please clarify.

            Ross McKenrick added a comment - - edited @martin Perhaps I didn't word my suggestion clearly enough or was just too verbose. Many of our users, including me, want to put the Blocked and/or Dropped columns to the far left or far right of our boards so they don't interrupt the visualization of the standard workflow (Not Stated->In Progress->Done). Not sure how adding the status to the card or your other suggestions address this. Please clarify.

            Many thanks for this Suggestion, however this is not something we plan to add to JIRA Agile at this time.

            This could be solved using Card Layout and adding the status to the card, or by using swimlanes or card colours.

            https://confluence.atlassian.com/display/AGILE/JIRA+Agile+6.6+Release+Notes
            http://blogs.atlassian.com/2014/09/jira-agile-6-6-now-available/

            Regards,
            JIRA Agile

            Martin (Inactive) added a comment - Many thanks for this Suggestion, however this is not something we plan to add to JIRA Agile at this time. This could be solved using Card Layout and adding the status to the card, or by using swimlanes or card colours. https://confluence.atlassian.com/display/AGILE/JIRA+Agile+6.6+Release+Notes http://blogs.atlassian.com/2014/09/jira-agile-6-6-now-available/ Regards, JIRA Agile

            Raghu S added a comment -

            I agree with Ross, it's painful to make column configuration and status mangement with your(Jira Agile) current assumption.

            Raghu S added a comment - I agree with Ross, it's painful to make column configuration and status mangement with your(Jira Agile) current assumption.

              Unassigned Unassigned
              5633ffded850 C. Ross McKenrick
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: