Configuration Fields
Field | Default | Description |
---|---|---|
Condition 1 |
| |
Condition 2 |
| |
Issues to update | %original_key% | Defaults to the issue being transitioned. Is a comma-separated list of one or more issues to be updated with the configuration provided |
JQL query |
| Query that is run to provide substitution variables including %jql_result_count%, %jql_result_list%, and %jql_result_1%. The query will be run once unless the field contains an entry specific subsitution variable, in which case the query will be run for each different entry value. |
Summary | %same% | Set issue summary field |
Transition |
| Transition name or ID. Defaults to no transition. When doing a transition, only fields available on the transition screen will be updated. The original issue being transitioned can not participate in another transition. |
Description | %same% | Set issue description field |
Project | %same% | Set project when creating issues |
Issue type | %same% | Set issue type |
Priority | %same% | Set priority |
Reporter | %same% | Set priority |
Assignee | %same% | Set assignee |
Affected versions | %same% | Set affected versions from a comma-separated list of version names |
Fixed versions | %same% | Set fixed versions from a comma-separated list of version names |
Components | %same% | Set components from a comma-separated list of component names |
Due date | %same% | Set due date. Use work to exclude non-working days (example: 5 work). |
Time tracking | %same% | Set original and remaining estimate |
Issue security level | %same% | Set security level for the issue |
Labels | %same% | List of labels to be set on entry issue |
Link |
| Adds a link to the issue |
Copy links | All link types | Copy one or more links from the issue key (or keys) provided to the issue. By default, all link types will be copied from each issue key specified. Specify a comma-separated list of link types to subset the copy to only those issue types. |
Copy remote links | All remote link types | Copy one or more remote links from the issue key (or keys) provided to the issue. By default, all remote link types will be copied from each issue key specified. Specify a comma-separated list of remote link types to subset the copy to only those issue types. |
Attachments |
| Issue key. If specified, attachments will be copied from the issue to the entry issue. |
Watchers | %same% | Add watchers from a comma-separated list of user IDs |
Comment |
| Comment added to entry issue |
Comment security | None | Security group or role for the comment. |
Copy parent issue custom fields |
| A comma-separated list of custom field names or IDs - each field is copied from the parent issue |
Copy original issue custom fields |
| A comma-separated list of custom field names or IDs - each field is copied from the original issue |
Set custom field |
| Set the value of a specific custom field identified by its name or ID. For date fields, there is an option to specify a date offset (in days) that will be used to adjust the value. Use work to exclude non-working days (example: 5 work). |
Acting user | Transition user | Provides a way for some permission checking and access to be done under a user different than the user doing the transition. This allows the workflow designer more flexibility to do actions for the user that they normally would not be able to do outside of the workflow. Tip: How to act on an issue for the assignee. |
Environment | %same% | Set the environment field |
Notes |
| Allows the workflow designer to document the post function |
Parent issue
If the issue is not a subtask, then the parent issue is the same as the original issue - the issue that originally started the transition.
Log a request with our support team.
Confluence®, Jira®, Atlassian Bamboo®, Bitbucket®, Fisheye®, and Atlassian Crucible® are registered trademarks of Atlassian®
Copyright © 2005 - 2024 Appfire | All rights reserved. Appfire™, the 'Apps for makers™' slogan and Bob Swift Atlassian Apps™ are all trademarks of Appfire Technologies, LLC.