Workflow Transition Properties

1 New viewing/editing experience
2 About workflow properties
3 Extender for Jira workflow properties
4 Available workflow properties

New viewing/editing experience

Available since v. 1.37.*

Workflow properties now looks like workflow function with a simple management interface and property suggestions.

About workflow properties

You can use workflow properties to implement restrictions on certain steps or transitions of a workflow.

For details on how to implement workflow properties (i.e. step and transition properties) in your workflow, please refer to Working with workflows.

Extender for Jira workflow properties

Name	Type	Values	Notes	Available

Name	Type	Values	Notes	Available
`extender.customer.comment.hide`	Status	`true` or empty	Allows you to hide the comment from the issue view in the customer portal Full documentation with examples you can find here → Workflow Transition / Status properties	Since v. 2.6.*
`extender.tab.condition.exclude`	Transition	`true` or empty	Allows you to hide the transition from Issue Conditions Validator tab Full documentation with examples you can find here → Workflow Transition / Status properties
`extender.customer.transition.comment.required`	Transition	`true` or empty	Forces a comment to be required on the transition available in the customer portal Full documentation with examples you can find here → Workflow Transition / Status properties
`extender.transition.color` `extender.transition.submit.color` `extender.transition.cancel.color`	Transition	`Color`	Allow you to manage the color of the specific button. You can choose from the example buttons or you can easily define the color yourself. Full documentation with examples you can find here → Workflow Transition / Status properties
`extender.transition.prefix` `extender.transition.suffix` `extender.transition.submit.prefix` `extender.transition.submit.suffix` `extender.transition.cancel.prefix` `extender.transition.cancel.suffix` `extender.transition.title.prefix` `extender.transition.title.suffix`	Transition	`Html` , `emoji` etc.	Allows you manage the prefix/suffix of specific button/title. You can add a piece of HTML code, emoji, etc. Full documentation with examples you can find here → Workflow Transition / Status properties

Available workflow properties

There are a few workflow properties which you can use in a transition or step of a workflow. Here are some helpful links:

Jira API Documentation - Jira Workflow constant values

Name	Values	Notes

Name	Values	Notes
`jira.field.resolution.exclude`	Resolution `id`	Add comma-separated resolution ids to the transition properties where you want to not show certain resolutions
`jira.field.resolution.include`	Resolution `id`	Add comma-separated resolution ids to the transition properties
`jira.i18n.submit`	i18n property key	Transition (usage: action submit button name)
`jira.i18n.title`	i18n property key	Transition (usage: action name, etc.)
`jira.issue.editable`	`true`, `false`	References: Working with workflows
`jira.permission.*`	`jira.permission.[subtasks.]{permission}.{type}[.suffix]` `[subtasks.]` is optional - If included the permission is applied on the issue's subtasks. If not the permission is applied on the actual issue. `{permission}.` - is a short name specified in Permissions class like admin, use, sysadmin, project, browse, create, edit, scheduleissue, assign, assignable, attach, resolve, close, comment, delete, work, worklogdeleteall, worklogdeleteown, worklogeditall, worklogeditown, link, sharefilters, groupsubscriptions, move, setsecurity, pickusers, viewversioncontrol, modifyreporter, viewvotersandwatchers, managewatcherlist, bulkchange, commenteditall, commenteditown, commentdeleteall, commentdeleteown, attachdeleteall, attachdeleteown, viewworkflowreadonly `{type}` - type of permission granted/denied. The values can be group, user, assignee, reporter, lead, userCF, projectrole `[.suffix]` - An optional suffix to make the property unique when you have the same type added more than once! jira.permission.edit.group.1, jira.permission.edit.group.2 etc Example: jira.permission.comment.group=some-group jira.permission.comment.denied= jira.permission.edit.group.1=some-group-one jira.permission.edit.group.2=some-group-two jira.permission.modifyreporter.user=username jira.permission.delete.projectrole=10000 jira.permission.subtasks.delete.projectrole=10000	Step (usage: only to restrict permission to either roles, group, or users when issue is in that step) References: WorkflowBasedPermissionManager class description (API documentation) Permissions based on Workflow Status For link permissions `jira.permission.edit.group=jira-administrators` means that only Jira administrators can edit an issue (blog)
`opsbar-sequence`	Integer value greater than or equal to 0	Transitions on the 'View Issue' page