Workflow Advance mappings
Summary
This feature will auto-transition issues during Issue Creation via JEMH or to switch the workflow status when an external user comments by email. If the workflow advance rule is with a Project Mapping, it is scoped to that Project alone. If entered in the Default Project Mapping, it has the ability to be inherited through all Project Mappings, defined centrally.
Workflow Advance Fields
When Issue Type is | With Issue Status | Apply On | Execute Workflow Transitions | Last Transition Comment (Optional) |
---|---|---|---|---|
Applies mapping when issue is a specific Issue Type | Applies mapping when issue has a specific status. | Defines when the mapping should be applied. Create/Comment or Create and Comment. | Defines the transition to occur, CSV style (yes, there can be more than one) | Optional comment to be added to issue. |
JEMHC Configuration
See Profile > Project Mappings > Issue > (edit) > Workflow Advance
Adding a Configuration
After editing Profile > Project Mapping > Issue, select Add Workflow Advance Mapping:
Then fill in the blanks:
Example Advance Mappings
Transitioning due to an external comment (Action Needed)
In this example, the expectation is that previously, the issue was set to Waiting on Customer, such that going back to Action Needed makes sense:
Example Workflow:
When Issue Type Is | With Issue Status | Apply On | Execute Workflow Transitions | Last Transition comment (optional) |
---|---|---|---|---|
Support | Waiting On Customer | On Comment | Action Needed |
|
Transitioning from Closed (Reopen)
In this example, the expectation is that the issue will have been Closed, being subsequently commented on, needs to get back to Action Needed. In this example this is done through the Reopen transition:
Example Workflow:
When Issue Type Is | With Issue Status | Apply On | Execute Workflow Transitions | Last Transition comment (optional) |
---|---|---|---|---|
Support | Closed | On Comment | Reopen | What? Its not fixed?! We'll get right on this! |
Multiple Transitions
In this example the issue can be transitioned back into closed status (first Reopen Issue, then Closed Issue):
When Issue Type Is | With Issue Status | Apply On | Execute Workflow Transitions | Last Transition comment (optional) |
---|---|---|---|---|
Bug,Support | Resolved,Closed | On Comment | Reopen Issue, Close Issue | This issue is closed, please log new issues for new issues |
Conditional Transition to re-open or create new Issue
In this example, you may only want the workflow transition to apply for issues that were recently closed, whilst wanting to create new issues when an issue has been closed based on custom criteria.
To achieve this, the Pre-Processing | Issue creation on Comment Rejection Match feature will support new issue creation. Pre-Processing | Reject Comments When Issue Resolved For More Than Days will also limit this behaviour to only create new issues when the Issue has been closed for the number of days specified.
How to accomplish this?
Enable , allowing Pre-Processing | Issue creation on Comment Rejection Match
Include custom criteria (E.g. You could configure a set number of days that the Issue must be closed for, or supply JQL for more specific conditions).
Create a workflow transition that supports commenting and transitions the closed issue back to open.
When Issue Type Is | With Issue Status | Apply On | Execute Workflow Transitions | Last Transition comment (optional) |
---|---|---|---|---|
Bug,Support | Resolved,Closed | On Comment | Reopen Issue | Reopened due to comment activity before the 7 day rejection. |
Now, the comment will be rejected if the Issue has been closed for 7 days or more. Otherwise, the closed Issue will be re-opened due to the workflow transition being applied.
Need further customisation?
If you require more strict conditions for issue creation, please refer to Pre-Processing | Message Rejection for more information regarding custom JQL to create a new issue instead of commenting on the matching closed issue.