Restrict Moving an Issue into a Specific Issue type.

[luizduarte]

We need a way to prevent some specific issuetypes/workflows from being moved into.

In our case, we have issuetypes that have a specific approval workflows, but what happens is that users can move other issuetypes into them and bypass the approval transition, which also messes with some other metrics we use.

Is there a way to prevent this like we can prevent clones?(By specifing "issues can't be created in this workflow with this status with the clone function")

[Andrew Laden · Accepted solution]

Not ideal, but put them in a specific project.

In my setup, we have a specific project just for approvals. When something needs an approval. it creates a linked issue in that approval project, and the workflow blocks on waiting for the linked issue to be resolved. The approval is processed in that liked issue, and when it is approved the linked issue is close allowing the original issue to proceed. 

That said, there are other ways to bypass statuses in jira. You have to be very careful and restrictive if you want jira to be an absolute enforcer of workflow, and doing so may limit you in other ways. (ie block all moving of issues if you want to prevent users from moving issues to bypass workflow)

Jira works best when it is used to track and guide proper workflow, and have policies in place that can "remind" users to follow the procedures and not try to bypass them. If you user is unintentionally doing this, then that is a training issue. If they are intentionally doing it to bypass policy, that is an Audit/Security/HR issue. Jira is good a leaving an "audit trail" of changes in the history, made, so you will have evidence if the user did something to bypass workflow.

[Deleted user]

Hi @luizduarte ,

This configuration can be achieved with configuring Move Issue Permission to certain roles only project admins.

https://confluence.atlassian.com/adminjiracloud/managing-project-permissions-776636362.html

Regards,
Kishore

[luizduarte]

The problem is that most issues can be moved no problem, it's a few specific ones that shouldn't be moved into.

[Kavi]

@luizduarte Could you please let me know if you were able to achieve this?

We have exact scenario to implement.

Thanks,

Kaviraj

[luizduarte]

We managed to solve the issue with a combination of actions, first, we restricted moving issues to certain roles, and then trained the people in those roles and that were working on the tickets to check if someone was bypassing approval.

The other issue was cloning and there's a property you can place in a status that prevents cloning to that status.

It's not perfect but by working with the system and the people using it, we reached a good compromise.

Also helps that the people doing the approval aren't happy to have their approval misused.

[Kavi]

@luizduarte Thanks for the response.

We will check.

Thanks.