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

Workflow Properties to Limit Delete, Cloning, and Editing

Ann Rumenapp

In company-managed, Jira Cloud project, I have two workflows (PCR & Change Approval) that need restriction upon completing a card. The first (PCR) workflow works just fine to restrict edit, delete and cloning using the three properties: jira.permission.createclone.denied, jira.permission.delete.denied and jira.permission.edit.denied.

The second (Change approval) workflow has 5 transitions to close and all 5 transitions contain the 3 properties listed above and yet the workflow allows editing cards in the close status. Is there some sort of Jira limitation on properties when there are 5 transitions to the same status?

PCR Workflow:

PCR Workflow Properties.png

Change (approval) Workflow:

Change Workflow.png

Accepted answers

Trudy P Claspill

Hello @Ann Rumenapp

If you want to prevent those actions when the issue is in the Closed status then you need to click on the Status lozenge (not the transition) and add the properties to the Status (not the transition).

All comments

Trudy P Claspill

Hello @Ann Rumenapp

Ann Rumenapp

When I add the permissions to the Close status it applies to any workflow using that status correct?

Trudy P Claspill

Incorrect.

When you add Properties to a Status in a specific workflow it applies only to that status in that workflow, which will apply it to any issue that uses that workflow.

Ann Rumenapp

Oh awesome! This particular status is used in 80 workflows so I was chicken to update it.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud