Configuration Fields
Most fields are common to both create issue and subtask except where noted in the Limited column.
Field | Limited | Default | Description |
---|---|---|---|
Subtask condition | create subtask | Ignore if original issue is a subtask | Option to take when original issue is a subtask. This applies when the original issue is a subtask:
|
Condition 1 | Â | Â | |
Condition 2 | Â | Â | |
Summary | Â | Â | Set issue summary field |
Description | Â | Â | Set issue description field |
Entry parent | create subtask | Parent of original issue | Â |
Project | create issue | Original project | Set project when creating issues |
Issue type | Â | Bug or Subtask | Set issue type |
Priority | Â | Parent's priority | Set priority |
Reporter | Â | Current user | Set priority |
Assignee | Â | Parent issue's assignee | Set assignee |
Affected versions | Â | Â | Set affected versions from a comma separated list of version names |
Fixed versions | Â | Â | Set fixed versions from a comma separated list of version names |
Components | Â | Parent issue's components | Set components from a comma separated list of component names |
Due date | Â | Â | Set due date. Use work to exclude non-working days (example: 5 work). |
Time tracking | Â | Â | Set original and remaining estimate |
Issue security level | create issue | None | Set security level for the issue |
Labels | Â | Â | List of labels to be set on new issue |
Link | Â | Â | Adds a link to another issue after the new issue is created |
Copy links | Â | All link types | Copy one or more links from the issue key (or keys) provided to the new issue. The new issue key will replace the key specified for the copy. 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 new issue. The new issue key will replace the key specified for the copy. 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 new issue after it is created. |
Watchers | Â | Â | Add watchers from a comma separated list of user ids |
Comment | Â | Â | Comment added to new issue after it is created |
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). |
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, it which case the query will be run for each different entry value. |
Create multiple issues | Â | Â | |
Acting user | Â | Transition user | Provides a way to 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. |
Subtask default handling | create subtask | Â | Recommend to not select this option unless needed. Select to have JIRA default subtask create handling applied. Selecting this may override settings provided in the create configuration like setting fix versions. Defaulting behavior will be similar to how subtasks are created from the UI. Example scenarios where you may need this:
|
Environment | Â | Â | 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.