How do I add or edit Jira workflow categories?

[Frank Pete]

I am now implementing a Stage Gate process in Jira. This is to force our organisation throught a commercial assessment and through a risk assessment and quality control before releaseing a larger development task for development. 

In this process the cost benefit (commercial assessment) may lead to rejection of the development task.
The same applies for risk assessment.

For this purpose, I do need another workflow category 'Rejected'
 

[Nic Brough -Adaptavist- · Accepted solution]

You'll need to hack the core code of JIRA, those three categories are pretty much hard-coded into it.

[Mahesh S]

Nic, Are you people speaking about the 'Status Category' like 'To Do', 'In Progress' and 'Done'?

[Nic Brough -Adaptavist-]

The question said category, so I assumed he meant category.

[Mahesh S]

Pretty confused what Frank is referring to as workflow category 'Rejected'.

Status Category or Workflow status?

[Nic Brough -Adaptavist-]

He did not say status, he said category.  It's clear he doesn't mean project category, so it must be workflow category.

[Frank Pete]

There are tree categories today. ToDo, In Porgress & Done. 
Thinking about it, we can magage with the three as the process is actually

Evaluate = To Do

Evaluating process = In Progress

Evaluation done and task rejected = Done + new status = Rejected

Thanks anyway

[Azfar_Masut]

It goes back to your definition of 'Rejected'

To Do, In Progress and Done is the highest level of the status category which should suffice. 

Rejected is not vague/general enough to become a category. Eg.: I cant think of a status which could become under the category Rejected. However, Rejected can instead be categorized as Done, as when an issue is rejected, its usually the end of the issue cycle. And you set 'Rejected' as the resolution instead. (which is the reason why resolution option exist in the first place)

Alternatively, if your definition for rejected is that the issue is rejected, but pending for a review, you should set it the issue as either 'In Progress' or 'To Do'. Both could work depending to how you handle a 'Rejected' issue in your workflow.

[Azfar_Masut]

It goes back to your definition of 'Rejected'

To Do, In Progress and Done is the highest level of the status category which should suffice. 

Rejected is not vague/general enough to become a category. Eg.: I cant think of a status which could become under the category Rejected. However, Rejected can instead be categorized as Done, as when an issue is rejected, its usually the end of the issue cycle. And you set 'Rejected' as the resolution instead. (which is the reason why resolution option exist in the first place)

Alternatively, if your definition for rejected is that the issue is rejected, but pending for a review, you should set it the issue as either 'In Progress' or 'To Do'. Both could work depending to how you handle a 'Rejected' issue in your workflow.

[Azfar_Masut]

How the hell do i delete comments here?? LOL

[Nic Brough -Adaptavist-]

You don't.  It makes a mess of the conversation threads, so it's discouraged.

You can edit them and delete the content, but that's just rude.

[Patrick Herrington]

This really should be added in.  For instance, why is there not a testing category?  It could include Unit, QA, UAT.  "In Progress" depends on the scope you are looking at.

[Marc Moroz]

I agree with Patrick.  For development teams, it helps to have a way of grouping some statuses into buckets that represent Development, Validation, User Acceptance, etc.  Having all these as In Progress makes it hard for us to get good info out.

[Mahesh S]

Please create a new status 'Rejected' (if not existing) from JIRA Administration-> Issues-> Statuses -> Add a new status. Add the new status to your workflow by referring this: https://confluence.atlassian.com/display/JIRA/Configuring+Workflow

Later, you can add this status to your agile board as well if required as https://confluence.atlassian.com/agile/jira-agile-user-s-guide/configuring-a-board/configuring-columns

[Mouli]

Needed a Blocked Status for my issues. Achieved it thru this!

Would have been happy had i got a Category for this(so that i could define a specific color & symbol).. but gotta make do with whats available.

[Paul Denize]

> To Do, In Progress and Done is the highest level of the status category which should suffice. 

I agree these should be more flexible.  I'd love a category "Waiting on Third Party" making it clear the person it is assigned to is not the one doing the work but monitoring those that are.  And the colour of the status seems to be controlled by the category so having something that could stand out would be good too.

I read this whole thread "How do you...." and it seems full of why would you answers.  Nobody has yet said you do it by .... or you cant. 

[Nic Brough -Adaptavist-]

Yes we did, see the first answer.  Granted it's a couple of years old, but it's still right.

[Pamela Rocamora]

Hi I have the same issue as Frank. I want to add a new STATUS Category (like To Do, In progress and Done)

[Nic Brough -Adaptavist-]

The original answer stands.

[Jo Vasev]

Hi I have the same issue as Frank. I want to add a new STATUS Category (like To Do, In progress and Done)

Is this possible yet?

[Nic Brough -Adaptavist-]

No, and it never will be - all these extra categories mentioned (so far) are really mostly status within "in progress" (and a couple are to-do or done)

[Azfar_Masut]

It goes back to your definition of 'Rejected'

To Do, In Progress and Done is the highest level of the status category which should suffice. 

Rejected is not vague/general enough to become a category. Eg.: I cant think of a status which could become under the category Rejected. However, Rejected can instead be categorized as Done, as when an issue is rejected, its usually the end of the issue cycle. And you set 'Rejected' as the resolution instead. (which is the reason why resolution option exist in the first place)

Alternatively, if your definition for rejected is that the issue is rejected, but pending for a review, you should set it the issue as either 'In Progress' or 'To Do'. Both could work depending to how you handle a 'Rejected' issue in your workflow.

And as Nic said, not possible. It's hardcoded