Defect in JIRA v4.1.2?

LSYH June 29, 2014

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
Answer accepted
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 29, 2014

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...

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 29, 2014

(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 Sign up to answer