nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to differ "create issue" permission in 2 workflows in 1 project?

Sandra Meessen

Hello, I have 1 Jira project with 1 permissions scheme but with 2 workflows (each for other issuetype). Workflow A my whole userpopulation may create the issues, but in my workflow B only 1 certain group. How do I define this on the "create issue" transition in my workflow B? I can only set a validator on the permission? Thank you for your help.

Accepted answers

Ollie Guan

Hi @Sandra Meessen,

I think you need to configure the add validator in the workflow

All comments

Ollie Guan

Hi @Sandra Meessen,

I think you need to configure the add validator in the workflow

Alexey Matveev

Hello,

You should add a validator to your workflows. If you do not have a validator you need, you can look for add-ons.

Sandra Meessen

At the moment I use "permission validator" and set "only users with permission "create issues" can execute this transition", but due to my other workflow my entire userpopulation has permission to create issues. So for my 2nd workflow I need a way to narrow down this to 1 specific little group. Is this possible with this below set of validators?

Create issues - validators.JPG

Ollie Guan

Hi @Sandra Meessen，

You can try the following plug-ins:

https://confluence.snapbytes.com/display/JEP/User+in+project+role+validator

https://apps.decadis.net/display/JWT/Only+users+in+a+field

Grigory Salnikov_0hffsd

Hi @Sandra Meessen!

I think you can still use a regular Permission validator. You just need to find a permission that the second group has an the first one lacks. If their permissions are identical you can grant some permission and use it in your validator.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server

permission