...
Setting | Details | ||||||
---|---|---|---|---|---|---|---|
Description | A description of the workflow rule. This may be useful for others who see this configuration. | ||||||
Workflow Name | Name of the workflow the rule is to be applied against. | ||||||
During | Defines what event will trigger the transition. There are three options:
| ||||||
Run Condition | Controls which user will drive the workflow transition. There are two options:
| ||||||
Issue Types
| Define which issue types the issue has to be in for the rule to be triggered. Only Issue Types valid for the workflow defined in the Workflow Name will appear. If none are selected then this restriction will be ignored. | ||||||
Statuses | Define which statuses the issue has to be in for the rule to be triggered. | ||||||
Transitions | Define what transition sequence to perform, i.e. Pending External > Action Needed. You can also carry out multiple transitions: Pending External > Action Needed > Resolved. | ||||||
Properties | Optional. Apply workflow properties to the transition to meet special transition conditions. To set the resolution in a transition you need to use the numeric ID that can be seen by hovering over EDIT in the Jira > Issues > Issue Attributes > Resolutions list:
therefore to set that resolution you would use:
| ||||||
Run As Condition | What user to run the transition as. This enables JEMH to carry out transitions that require different identities (i.e. Assignee). There are three options:
|
...
Using the workflow below, we want an issue to be set to Pending External when the assignee comments and Action Needed when another user comments back.
This Only Issue Types valid for the workflow defined in the Workflow Name will appearThis is the rule for transitioning the status from Action Needed to Pending External when the assignee comments.
...
Once the mapping has been created the Workflow Auto Advance Rules can be added in the same way as we did earlier in the step-by-step guide. What will happen is that when JEMH matches on a project mapping rule and finds that there are no Workflow Auto Advance Rules to apply in that mapping it will then check the default mapping to see if there are any rules there, if any rules are found and the project has a matching workflow then they will be applied.
Issue Type Restriction
Status | ||||
---|---|---|---|---|
|
If you require further issue type restriction in the Workflow Auto Advance rule then select Issue Type(s) and save by clicking the submit button.
Setup
...
View
Issue Type column will show you the currently saved issue types which which are valid to pass the issue type restriction. If there is an invalid issue type for the current workflow; then it will be highlighted in red with a message, “The issue type selected is invalid”. This can typically happen if a user is importing a profile from one system to another.
...
Related Articles
Filter by label (Content by label) | ||||||||
---|---|---|---|---|---|---|---|---|
|