Configuring Jira Agile columns for NotStarted, InProgress and Done

I am using a custom workflow with Jira Agile 6.3.1. I have a total of 11 columns with the appropriate statuses mapped out, as shown below.

How can I configure the colour coding of the columns? The red-yellow-green is reflected as a summary on the sprint planning view, but currently this means that an issue will only be marked as done when it is released into production, not when it has passed testing and is ready for release. This means that the red-yellow-green status is next to useless, as almost every ticket will be In Progress (see below):

In this case, we are one day away from the end of our sprint, and nearly every issue has passed testing and is ready for release, which in our book counts as done - but Jira Agile doesn't agree!

4 answers

1 accepted

5 votes
Accepted answer

Unfortunately, based on my research, the answer is "Don't use JIRA Agile that way."

I am struggling with the same problem, and I'm about to just give up and split it into two boards, one a Scrum board that marks an issue as "Done" when it's passed to QA, and a second Kanban board that tracks the issues through the promotion environments. That way you can at least measure burn-down at the point where developers are done with it, even if it doesn't really mean ultimately that the issue itself is "done" (i.e. through QA and deployed).

Seems trivial to make columns assignable for purposes of estimation, but given it took 2 months for anyone to even so much as acknowledge your question I guess I shouldn't be surprised if this never makes the cut.

We will be using two boards as well. Thanks for the idea Curtis!

+1 - this seems like a pretty obvious requirement given the flexibility of configuring the scrum board. I cant believe many teams use just 3 columns in real life, and mandating that all but the first and last columns are "in progress" (yellow) renders the colouring (and the potentially very useful summaries on the plan page etc) utterly useless.

It's a shame that they don't use the Resolution field to check for completion - if it's unresolved and in the Open (or initial) state, it must be Not Started, if it's unresolved and not in the Open state, then it must be In Progress; if it has a resolution (fixed, won't fix, or whatever) then it can be considered Done regardless of its current state.

We couldn't do that (use Resolution for Done) because we have a Review state. Once an issue is worked on, it gets a Resolution. Next it is reviewed by the team and if it passes it goes to Done. If it fails the first check, it goes back to the fixer for more work - all within the same sprint cycle.

Please, let people decide on such a simple thing like having several "Done" statuses, even if it is not orthodox. Anyone filed a request for this already?

hello, there's also the problem about the checkbox attached to a status : this checkbox is supposed to be ticked and set the Resolution field to Done when an issue is transitioned to this status. It apparently does set the issue's Resolution field to Done, but when you close your sprint, if your status is NOT in the green column at the left, then your issue is not considered really done. And you get the alert about issues not completed.

However, if your status is in the green column, then even if the checkbox is NOT ticked, all the issues which are in this status are considered completed in the sprint (burndown chart OK, no alert when you close the sprint...)

It seems that JIRA Agile considers issues are completed when they are in the green column, regardless of the Resolution field state.

In my humble opinion, it looks like a bug.

hello,

Am I the only one who finds it weird that statuses MUST be in the last column to be considered Done, regardless of the Resolution checkbox being ticked or not ?

Bump - does anyone have a solution?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Apr 22, 2018 in Jira Software

How-to setup a secured Jira Software 7.9.0 on Ubuntu 16.04.4 in less than 30 minutes

...PermissionsStartOnly=true User=www-data Group=www-data ExecStart=/opt/jira/bin/startup.sh ExecStop=/opt/jira/bin/shutdown.sh TimeoutStartSec=120 TimeoutStopSec=600 PrivateTmp=true [Install] WantedBy...

2,107 views 14 13
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you