Adding new statuses seem to impact a user's JQL

[Sau Kan]

I plan to make improvements to the current Jira workflow by adding new statuses and transitions. However, I am facing resistance where this change will impact a user's many JQL. How can I go about this?

[Jack Brickey · Accepted solution]

Hi Sau,

I suspect what you're referring to hear is that you have users they have saved filters that include specific statuses. And when you add new statuses to a workflow their filter breaks. Is this the case or do you mean something different? Yes that is what you're referring to it could be that the issue lies with poor filter definition. 

[Bill Sheboy]

Hi @Sau Kan -- Welcome to the Atlassian Community!

Yes, and...to what Jack suggests:

Perhaps pause to consider why the team is changing their workflow/statuses/transitions: what problem are they trying to solve?  Raising visibility to that will help people understand the change and work collaboratively to also improve their saved filters/reporting.

Kind regards,
Bill

[Sau Kan]

Thank you for your reply Jack and Bill. You're both correct and I agree that the user's  saved filter probably needs improving. More importantly, it cannot be the only reason and from ONE user only to prevent a workflow that needs improving in order for the scrum team to deliver the product more efficiently, create more visibility & transparency, and reduce assumption. I was hoping someone here could advise on how the user could change his JQL e.g. bulk update may work if it's simply renaming a status.

If I do not make this change to the workflow for one scrum team, it will eventually happen across the board to multiple scrum teams. The user will need to change his JQL filter at some point anyway.