It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Restrict Moving an Issue into a Specific Issue type.

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")

2 answers

1 accepted

1 vote
Answer accepted

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.

Hi @luizduarte ,

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

Screenshot 2019-10-16 at 11.22.10 AM.png

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

Regards,
Kishore

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

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

334 views 1 3
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you