Learn how to build a simple Jira Cloud workflow suitable for
pharmaceuticals, medical devices, and other highly regulated industries.
In four easy lessons, I’ll walk you through converting an off-the-shelf Jira workflow from Atlassian into a fully compliant GxP workflow with:
- Controlled flows to ensure established business rules are followed
- Field validation to verify user data as the workflow progresses
- User permissions to configure which team members can move electronic records through different steps of the workflow
- Status-based workflow controls to protect the integrity of records that have been reviewed or approved.
- Electronic signatures compatible with 21 CFR Part 11 to streamline your approval process into a single workflow.
Additional resources
Links mentioned in the training:
Example workflow properties (from Lessons 3 and 4)
For open statuses (Lesson 3):
- jira.permission.move.projectrole = 10002
- jira.permission.delete.denied
For closed statuses (without the signature app) (Lesson 3):
- jira.issue.editable = false
- jira.permission.attach.denied
- jira.permission.attachdeleteall.denied
- jira.permission.attachdeleteown.denied
- jira.permission.comment.denied
- jira.permission.commentdeleteall.denied
- jira.permission.commentdeleteown.denied
- jira.permission.commenteditall.denied
- jira.permission.commenteditown.denied
- jira.permission.link.denied
- jira.permission.move.denied
- jira.permission.delete.denied
For closed statuses (with the signature app) (Lesson 4):
- jira.permission.edit.projectrole = 10003
- jira.permission.attach.projectrole = 10003
- jira.permission.attachdeleteall.denied
- jira.permission.attachdeleteown.denied
- jira.permission.comment.projectrole = 10003
- jira.permission.commentdeleteall.denied
- jira.permission.commentdeleteown.denied
- jira.permission.commenteditall.denied
- jira.permission.commenteditown.denied
- jira.permission.link.denied
- jira.permission.move.denied
- jira.permission.delete.denied