-
Suggestion
-
Resolution: Duplicate
-
None
When we create a new sub-task via automation, we should be able to set a parent id besides of "current issue" or "trigger issue". At this moment, we can only set the current issue or trigger issue. Even if we try via additional field, it won't work.
- duplicates
-
AUTO-468 Support for field IDs instead of just field names in Automation, so rules don't break when fields are renamed, and to support custom fields with the same name
- Gathering Interest
[AUTO-386] When we create a new sub-task via automation, we should be able to set a parent id besides "current issue" or "trigger issue"
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
Component/s | Original: Automation [ 68402 ] | |
Component/s | New: Trigger - Other [ 70304 ] | |
Key |
Original:
|
New:
|
Workflow | Original: JAC Suggestion Workflow JSWCLOUD [ 4269629 ] | New: JAC Suggestion Workflow 3 [ 4344646 ] |
Project | Original: Jira Software Cloud [ 18511 ] | New: Automation for Cloud [ 22610 ] |
Summary | Original: When we create a new sub-task via automation, we should be able to set a parent id besides of "current issue" or "trigger issue" | New: When we create a new sub-task via automation, we should be able to set a parent id besides "current issue" or "trigger issue" |