From the course: Jira: Managing Custom Workflows

Unlock this course with a free trial

Join today to access over 25,300 courses taught by industry experts.

Using properties

Using properties

Finally, let's discuss workflow properties. Now this section comes with a warning. The documentation warns that properties can be, well, unpredictable. So just keep this in mind when you're building and testing. A property is a key-value pair used to further customize statuses and transition behavior. Let's explore the three that I use the most. The first is jira.issue.editable. In the screenshot, I've applied jira.issue.editable to the final workflow status and set the value to false. This means information in issues in the done status cannot be changed. This is sometimes useful in a highly regulated environment. jira.issue.editable works in server and data center. For cloud, use the jira.permission.edit.denied property instead. Next is jira.field.resolution. include. In the screenshot, I've applied this property to the done transition. The property values 10000, 10001, and 10002 represent the standard done, won't do, and duplicate resolutions. You can see the ID of each resolution…

Contents