Centrally Managing Status-to-Resolution Mapping Across Jira Workflows

Justin Heidema

My organization currently manages roughly 20 different statuses within the 'Done' category, spread across hundreds of workflows and many Jira projects. Each of these statuses logically corresponds to specific resolutions. For example, every workflow that includes a "Delivered" status should automatically assign the resolution "Done" when a ticket transitions to that status.

According to Atlassian's documentation, there seem to be two approaches for configuring ticket resolutions:

1. Manually configure the resolution setting within each workflow individually.

2. Require users to manually select a resolution when transitioning tickets.

Ideally, I'd like a central location or global configuration where I can define and manage these status-to-resolution relationships just once, rather than repeatedly configuring this for every new workflow.

Is there an existing Jira feature, marketplace app, or workaround that can centrally manage these mappings? Is managing these mappings centrally considered best practice, or are we unintentionally deviating from Jira's recommended workflow management approach?

I'd greatly appreciate insights or experiences from others who've addressed similar challenges.

John Funk

Hi Justin,

No, there is no global way to configure/implement this. The two options are as you have described. One question is why so many Done statuses? Second is to have as few workflows as possible with commonality in them. You can add conditions to the workflows that apply some statuses to some projects and not others, thereby sharing the workflows across multiple projects. 

Also, you can start with a well created workflow and then copy it to create new workflows. That way the statuses are already there and post functions are in place.