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; } } }

What is the purpose of the “CREATE” parameter in the jira.permission.* workflow property?

Marcelo Viana de Siqueira

I read the Atlassian documentation about workflow properties:
https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/

There is a parameter called CREATE for the jira.permission.* property, but the documentation does not clearly explain what it does.

In my test environment, I have a project XPTO with issue types Bug and Task, each using its own workflow. Both user groups ABC and XYZ have full permissions (create, edit, etc.) in the project.

In the TO DO status of the Task workflow, I added the property expecting that only users from group ABC could create Tasks.

Key	Value
jira.permission.create.group	ABC

However, users from group XYZ can still create Tasks normally.

Can anyone explain what the CREATE parameter is actually used for in the jira.permission.* property and whether it should affect issue creation?

Accepted answers

Ignacio Vera

@Marcelo Viana de Siqueira
The jira.permission.create property doesn’t control who can create new issues, it only applies to actions performed on existing issues once they’re already in that status (for example, creating sub-tasks)

If your goal is to restrict who can create new issues, you can add a condition or validator on the Create transition instead and require that the creator must belong to group ABC.

All comments

Brant Schroeder

@Marcelo Viana de Siqueira The jira.permission relates to permission so take a look at the permission scheme. The create has to do with the create permission on a project to create issues as you have explained but is limited to the specific work item it is associated with. It will allow the group associated with the permission on the workflow to create issues when that issue is in that status. It should allow the users of that group to create sub-tasks for that issue for example while it is in the status.

Ignacio Vera

If your goal is to restrict who can create new issues, you can add a condition or validator on the Create transition instead and require that the creator must belong to group ABC.

Marcelo Viana de Siqueira

@Ignacio Vera

Thank you for the explanation, that clarifies everything.

I now understand that the jira.permission.create.* workflow property does not control who can create a new issue type in a project. Instead, it is related to creation permissions inside an existing issue, such as creating sub-tasks or linked issues while that issue is in a specific status.

In my case, both groups already had the Create Issues permission in the project’s permission scheme, so the property had no effect.

This explanation was very helpful and I appreciate the detailed guidance.

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

jira-data-center

data-center