Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
0
-
5
-
Description
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
Currently we've got 'Edit request type' THEN action, but it cannot change request type, when related issue type change is required.
That's because issue type change is a complex operation, that if implemented generically will require:
- workflow check and migration to another workflow if that's required
- field configuration check and migration to another field configuration if that's required
...
That said, there are several ways to support it in automation:
- modify issue request type and issue type only these has compatible workflows and field configurations
- implement simplified version of JIRA's 'Move issue' wizard inside automation or somehow reuse existing one
...
Attachments
Issue Links
- is related to
-
AUTO-549 New trigger for "Issue moved to project" and new action for "Move issue between projects"
- Gathering Interest
- relates to
-
AUTO-551 Issue workflow/field configuration migration in automation
- Closed
-
AUTO-601 Add automation trigger and action for Move Issue
- Closed
-
JSWCLOUD-22679 New Automation action to move issues between projects
- Closed
-
JIRAAUTOSERVER-244 Action to change sub-task parent (or move a sub-task for one project to another)
- Gathering Interest
-
JSWSERVER-24922 automation moving item to next sprint based on dependencies
- Gathering Interest
- is cloned from
-
QUALITY-363 Loading...