How can I set a condition on the initial transition in a Jira-workflow?

[Anette Bengtsson]

Hi!

I need to find a way to prevent people in a specific project role from creating issues, but allow them to do other transitions in the workflow.

The project role does not have permission to create issues. I tried to use the validator in the transition between Create and Open, and set "Only users with Create Issues permission can execute this transition." But IT DOES NOT WORK!

Therefore I d like to try and set a Condition for the transition - but it is not possible...

I m very grateful for any ideas - THANK YOU!

Anette Bengtsson

Swedish Board of Agriculture

[Anette Bengtsson]

Thank you for the help! It worked when I removed the Current Assignee from permission to create issues! YES!!!

[Anette Bengtsson]

I removed Current Assignee from the Create permission in the permission scheme - and person "AB" in project role "B" still can create issues in my test-project...

[Cyril Egan]

I think your problem is because you have the "Current Assignee" set to be able to create. If you remove that setting in the permission scheme and test then I expect that the user in Project Role "B" won't be able to create.

[Anette Bengtsson]

From the create permission in the permission scheme:

• Project Role (Projektadministratör) (Ta bort)
• Project Role (Ärendeansvarig) (Ta bort)
• Project Role (Kravanalytiker) (Ta bort)
• Project Role (Designer) (Ta bort)
• Project Role (Utvecklare) (Ta bort)
• Current Assignee (Ta bort)

From the project administration:

Person "AB"

• is in project role "Titta" for the test-project
• is in group Jira-users
• is not set as Current Assignee in the created issue.

The group Jira-users has no permissions in the test-project.

[Nic Brough -Adaptavist-]

Ahh, I see. No, B shouldn't be able to create issues. They must be getting it via a group, as Cyril suggests, or something else in the creation permission.

Could you list everything in the "create" line in the permission scheme?

[Cyril Egan]

Are there any 'Groups' configured in Project Role "A" on the project?

[Anette Bengtsson]

Oh, sorry... I mean like this: Only the project role "A" has Create Permission in the Permission Scheme. In the workflow "Only users with Create Issues permission can execute this transition" is set in the transition between Create and Open.

And the problem is that people in project role "B" can create issues.

I am surely missing something but what?

[Nic Brough -Adaptavist-]

So no-one can create issues. You need to add the role in there.

[Anette Bengtsson]

No, Anonymous don t have Create permission.

[Cyril Egan]

Does the group 'Anonymous' have the create permission?

[Anette Bengtsson]

Thanks for your answers! But...

• The project role does not have permission Create Issues in the Permission scheme
• The users are not members in any groups or roles that can create issues

and it still does not work!

Any ideas?

[Renjith Pillai]

If in your permission scheme does not allow the Create Issues permission to this project role it should work fine. Are these users getting permissions from other group membership due to which they are able to create issues?

[Nic Brough -Adaptavist-]

You should use the permission scheme to control roles access to "create" in the project.

[JamieA]

You should, but it would be very nice if you could put conditions on the create step, as you can have much greater control with conditions than you get in the permission scheme.

[Nic Brough -Adaptavist-]

Yup, I'd like that too ;-)