Permissions and rules by issue types

[Сергей Баев]

Is it possible to do such things in a next-gen project?

1. Only the team leader can create an issue "Task". But issues "Subtask" for initial issue can be added by every user.
2. Only an issue "Subtask" can be moved using a certain transition in the general workflow.

[KAGITHALA BABU ANVESH]

Hi,

A) It's not possible to restrict only some users creating an issue type.

B) Project settings --> issue types --> Edit Workflow --> Add Rule

according to B , you can one user / Role can permit to transit issues.

Thanks,

Anvesh

[Сергей Баев]

Thanks for quick answer.

Paragraph A is clear.

About B. There is only one workflow for whole project. So what rule I've to use to prohibit using a certain transition for a type "Subtask" and to allow it for other types? Or maybe not a rule but some other tool?

[Daniel Ebers]

For B) this would require a different workflow per issue type (= here for the Subtask).
This is a feature that users can expect shortly, please see here for further details:
https://jira.atlassian.com/browse/JSWCLOUD-17434

[Сергей Баев]

Thanks Daniel!

I saw a banner about several workflows in a future. There is no other way to manage my problem, right?

[Daniel Ebers]

Depends on how far you would be willing to go, I mean, when somebody advises now to export all the data and start over with a Classic project, technically the individual would be right.
It would be a solution - but I do not assume it is worth the stress.
So - no nothing that I would be aware of that would set effort and outcome into a relation.