Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How can i add Sub Status to Incidents?

Vidhi Raman Chandra
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 7, 2025

Team

 

I want to streamline the incident status and keep it simple as New> In progress> Waiting for customer> Resolved> Closed

However under in progress i want to create Sub Status like Pending Dev/ Pending code fix and these are to be used when a incident moves to Dev queue to track what is the progress.

Similarly under resolved we would like to see Pending Release and once released it can move to resolved and closed

3 answers

1 accepted

2 votes
Answer accepted
Jaime Escribano
Contributor
May 7, 2025

Hi Vidhi! Glad to have you in the Community!

 

As @John Funk mentioned there is no way to have "sub-statuses" in Jira... but you can have sub-tasks.

 

This solution is not simple so I would ask giving it a good thought as to whether or not you really need it!

So, we want to create 2 new sub-tasks and add them to the issue type scheme Associating issue types with projects | Atlassian Support | Atlassian Documentation (This is so that they can have different workflows). You can name this issues something like "Incident Dev" and "incident deploy".

 

Then you would need to create two simple workflows with your desired statuses -> How to create workflows | Jira Work Management Cloud | Atlassian Support

 

Finally you would create an automation with the following pseudocode:

  1. When your issue is transitioned
  2. If-Else statement
    1. If the status is "In-Progress"
      1. Create a new Incident Dev sub-task
    2. Else if the status is "Pending Release"
      1. Create a new Incident Deploy sub-task

 

That way you may create queues where you keep track of your sub-tasks. You could also consider adding conditions to the workflow so that the incident is not closed if it has open sub-tasks.

 

When is this a good idea? -> Whenever the dev work and deployment have enough effort to be worth the extra complexity of keeping track of them.

 

When is it not? This will add a lot of complexity to your process and require maintenance in the long term. Keep that in mind if you decide to go ahead.

 

Let me know if you need help setting up this solution!

Vidhi Raman Chandra
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 7, 2025

Thank you @Jaime Escribano  this helps. I will consider this and also add an enhancement for the same

1 vote
Christopher Yen
Community Champion
May 7, 2025

You could create a custom field to hold that information and train your users to use it/incorporate screens as part of the workflow to fill out the custom field but with how JSM is setup I believe it would be better practice to create additional statuses to represent your sub statuses (making Pending Development and Pending Code Fix as available statuses in your workflow)

1 vote
John Funk
Community Champion
May 7, 2025

Hi Vidhi - Welcome to the Atlassian Community!

There are no "sub statuses" in Jira. You could create a regular status by the name you want and make it an In Progress category when you create the status. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events