Using Jira Cloud Workflow Properties in a Regulated Workflow

In this tutorial we look at restricting actions–such as deleting, moving, cloning, and editing–in Jira Cloud based on workflow status. This is an important strategy for creating compliance in a regulated workflow (GxP, 21 CFR Part 11, SOX, etc.).

Configuring a Company-managed Project

1. As a site administrator, go to Settings –> Issues –> Workflows.
2. Locate the workflow associated with your project, and select Edit.
3. Select the workflow status that you want to lock, and select Properties (or View properties, depending on your view).
4. Add the following properties:
   • To restrict deleting:  jira.permission.delete.denied
   • To restrict moving:  jira.permission.move.denied
   • To restrict cloning:  jira.permission.createclone.denied
   • Note:  To restrict editing, reference Episode 01.
5. Repeat Steps 3 and 4 for each status in your workflow that you want to lock.
6. When you’re finished, select Publish changes.  (Save a back-up if desired.) 

Configuring a Team-managed Project

1. As a project administrator, go to Project settings in your project.
2. Select Issue types.
3. Select a target issue type, and then select Edit workflow.
4. Select the workflow status you want to lock, and then select Properties in the sidebar.
5. Add the same properties described in Step 4 under Configuring a Company-managed Project (above).
6. Press Save.
7. Repeat Steps 5 and 6 for each workflow status you want to lock.
8. Select Update workflow.
9. Confirm the issue types you want to update, and press Save. 

Related Tutorials

• 01 – Locking Issues by Workflow Status in Jira Cloud

More Information

Find more strategies like this in my Quick Start Guide for Jira Cloud:  https://www.agile-innovations.tech/part-11

Learn more about Jira workflow properties here: https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/