Defect in JIRA v4.1.2?

Hi All,

we just migrated a project from JIRA v4.1.2 to another instance. In these cases we set the old project to read-only in order to being able the users to make comparisons with the new one. It just turned out that the users can change transitions! They have only Browse permissions and they cannot edit the issue i.e. edit Description, Summary or custom fields. BUT they can change statuses!!!!!

How can we restricct this?????

Thanks in advance,

Rumi

1 answer

1 accepted

0 votes

I suspect you've got the same problem in the source Jira as well, unless you have different workflows.

Anyway, the root problem here is that your workflow says "anyone can do this transition". Have a look at each transition, and add "conditions" to them to protect them. The easiest one is "must be in role X in the project" - then, don't add any users in the read-only projects...

(Oh, and this changes in Jira 6.3 - Atlassian have introduced an extra default permission to protect transitions by default)

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,801 views 11 18
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot