Dynamic Status

[robert_egan_305]

I have inherited a legacy JIRA environment with hundreds of statuses. A lot of them are very similar, like "PM Review", "QA Review", "SE Review", DevOps Review".... 

I would like to create a new class of status that supports a dynamic name such as "{0} Review", with the value of {0} set by the post function of the transition that leads to the status.

Status objects are created by the StatusManager (imagine that), and so I would like to implement my own StatusManager interface and replace it in the pico container. Is this even possible, and if so how would I go about it?

If it is not possible, or not recommended, how would you go about creating and using a custom implementation of the Status (or StatusManager) interface?

[Nic Brough -Adaptavist- · Accepted solution]

You won't be able to do this the way you're thinking.

A status is a label for a step in a workflow, they're not entities in their own right.  How would your status know what the {0} is supposed to be in different workflows?  And if a workflow has more than one of these status, then how would the unique display work at the status level?

The best you could do is to rip out all the places that render the status, replacing them with code that reads a property manually added to the workflow step when your admins are creating the workflows, and then displays the variable.

You would also need to think about how to rewrite the parts of the search with some way to understand which one people are looking for when they search by status, and a way to index the step property alongside the status.

Short story - you'll need to redesign and then rewrite a good chunk of Jira code code, not just tinker with the statusmanager part of it.

[robert_egan_305]

Thanks. I was beginning to think it was non-trivial, but I had no idea exactly how complicated it would be.