Restrict MOVE operation to Issue Type or Status

[David Meredith]

Hi all,

All of my IT SD agents need to be able to move issues between Incidents and Service Requests because they're VERY often incorrectly assigned and this impacts how our SLAs work. So they NEED the MOVE operation.

However they can also MOVE any Issue Type to a Change Record to ANY STATUS essentially bypassing every approval that we have in our Change workflow, which from a behavior and audit persective is bad....

Please can you advise if there is any way to prevent this? Ideally using the Out Of the Box functionality in JSM rather than another additional addon.

Or is there an existing feature request / bug that is likely to be implemented in my lifetime that I can add my voice to?

Many thanks,
Dave

[Darryl Lee]

Hi @David Meredith ,

I found the following threads that might have the same inquiry and the solution.

https://community.atlassian.com/t5/Jira-questions/How-do-i-restrict-moving-of-issues-to-a-particular-project/qaq-p/1443249

https://community.atlassian.com/t5/Jira-questions/Is-it-possible-to-restrict-moving-issues-based-on-project/qaq-p/913044

https://community.atlassian.com/t5/Jira-Software-questions/Prevent-issue-to-be-moved-into-a-specific-project/qaq-p/1842490

[David Meredith]

Hi Darryl,

Thanks for the info. I can see how these answers might address the problem for Jira Software maybe?

For JSM, we're actively encouraged to have REQ / INC / PRB / CHG issue types in the same project for Service Management purposes, so moving the CHG record to another project for the express purpose of preventing the MOVE operation doesn't make sense. Also, for those that do still need to make CHG records, they'll have access to that other project and have the capability of moving something there to any status they want.

ScriptRunner might be an option if we purchase it but really I'd have thought that this is a product issue? It seems to make crafting workflows redundent if you can just bypass all of them with a MOVE operation?