"sub status" in JIRA?

we have a workflow that is fairly basic from a top-level view: Open -> In Progress -> Resolved -> Closed.

This is useful from a management/client point-of-view. But internally, we would like to have greater precision in the "In Progress" status. For example: "Functional Design" -> "Functional Review" -> "Architectural Design" -> "Arch Review" -> "Dev" -> "Code Review" (or something of that nature). Is there any way to have "two levels" of statuses? (So the development details could be visible to the dev team, but "rolled up" into one general status for everyone else.)

2 answers

1 accepted

You can have multiple transitions within the same status. Say In Progress -> Functional design -> In Progress. And you can view the transitions that the issue has made and the transition time using the transitions tab on the bottom of the issue (asuming you have jira suite utilities plugin).

Other way can be to label the ticket as Functional design or anything else when it enters that phase. This way everyone will know which phase it is in. Again labels are searchable so will aid in management reporting.


I don't understand your first sentence. How can you have multiple transitions within the same status? Is there some documentation explaining this?

Hi. What rahul means you can add more transitions to each step inside your workflow. Note that one step needs a status the issue will be in if it is transitioned to this step. Read jira wiki about designing workflows and see the possibilities. Sub status is not supported

Oh I see. So you're suggesting something like:

[In Progress] -> (Begin Functional Design) -> [In Progress] -> (Begin Functional Review) -> [In Progress]

(where status is in brackets and transitions are in parenthesis).

That might work. I'll have to give it some thought. Thanks!

Unfortunately, one of the drawbacks to this approach is that there is no way to enforce the sequence of the sub-steps/transitions. ALL of the transition buttons will be available at the "In Progress" stage.

1 votes
Renjith Pillai Community Champion Jan 28, 2013

Yet another way is to define them as normal statuses and define an additional scripted field for the managers which shows the overall status.


There's a creative approach. Thanks for the great idea.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,063 views 13 18
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot