I have different JIRA Status(such as ToDo, In-progress, Grooming, UAT, etc..), i want combine status

Anantharaj_86od8v

Currently we have some different type of JIra ticket status, such as below example. 
But, I need to display the below status count in Two dimension filter Gadget/ Column Chart Gadget. I want to write a Script to retrieve the records by merging some of the status to be simple/user friendly statusmessage for high-level business understanding. something like below,

For example (from the below status):

BACKLOGS
TO DO
CANCELLED
GROOMING
READY FOR DEVELOPMENT

IN PROGRESS
TESTING
DONE

For example (I want to combine the status as below):
IN BACKLOGS  ( All above BACKLOGS)
REQUIREMENT(The above "TO DO" and "GROOMING" items only)

IN-PROGRESS (All above "READY FOR DEVELOPMENT", "IN PROGRESS",  "TESTING")
DONE ( The above "DONE")


How to write Jira Search Query/Script to combine the above JIRA status like that, so can use that Script to create the Gadget accordingly in JIRA DASHBOARD.?

Emre Toptancı [OBSS]

Hello @Anantharaj

I am not sure I understand your need perfectly but I believe you are trying to get a "Two Dimentional Filter Statistics" gadget, with one dimension being Status. The thing is, you want to display not each individual status, but you want to put them in status groups.

If that is the case, I am sorry but it can't be done with plain JQL.

I can recommend the following solution which requires a little configuration.

Create a Select List custom field named Status Group. Define all status group names as options of this field. Modify each transition in your workflow(s) and make sure that the correct status group name is set to this field in each transition. You can also update this field on existing issues using Bulk Change.

When this is all done, instead of using the Status field you can use the Status Group custom field to prepare your Two-Dimensional gadget.

The upside of this solution is: It doesn't require any additional apps. The downside is: It requires some configuration (proportional to the number of workflows/transitions you have) so it might be hard to build and maintain.

Hope this helps.