-
Suggestion
-
Resolution: Unresolved
-
None
-
0
-
Suggested improvements
- Automation Clone does not clone all data related to add-ons. This is noted when compared against the native Cloning feature in Jira which does include add-on data like Xray
- Extend clone issue action to optionally include cloning-related issues: Stories in epic, Subtasks, Linked issues.
- Include remote links (weblinks and confluence links) while cloning issue.
- is duplicated by
-
AUTO-214 Improve "Clone issue" action - add support for remote issue links when cloning
- Closed
-
AUTO-477 Improve create/clone issue error message for missing fields on a screen
- Closed
-
AUTO-481 Improve Clone Issue action - Automation Clone does not clone all data related to add-ons
- Closed
- mentioned in
-
Page Failed to load
[AUTO-148] Improve "Clone issue" action - option to include cloning related issues, clone add-on data, make cloning errors clearer
Remote Link | New: This issue links to "Page (Confluence)" [ 1016879 ] |
UIS | Original: 3 | New: 0 |
Description |
Original:
Suggested improvements
* Automation Clone does not clone all data related to add-ons. This is noted when compared against the native Cloning feature in Jira which does include add-on data like Xray * Extend clone issue action to optionally include cloning related issues: Stories in epic, Subtasks, Linked issues. |
New:
Suggested improvements
* Automation Clone does not clone all data related to add-ons. This is noted when compared against the native Cloning feature in Jira which does include add-on data like Xray * Extend clone issue action to optionally include cloning-related issues: Stories in epic, Subtasks, Linked issues. * Include remote links (weblinks and confluence links) while cloning issue. |
Labels | Original: Automation_Move_JSW | New: Automation_Move_JSW jsw-s13 |
Description |
Original:
Extend clone issue action to optionally include cloning related issues:
* Stories in epic * Subtasks * Linked issues. |
New:
Suggested improvements
* Automation Clone does not clone all data related to add-ons. This is noted when compared against the native Cloning feature in Jira which does include add-on data like Xray * Extend clone issue action to optionally include cloning related issues: Stories in epic, Subtasks, Linked issues. |
Summary | Original: Improve "Clone issue" action - option to include cloning related issues, clone add-on data | New: Improve "Clone issue" action - option to include cloning related issues, clone add-on data, make cloning errors clearer |
Summary | Original: Improve "Clone issue" action - option to include cloning related issues | New: Improve "Clone issue" action - option to include cloning related issues, clone add-on data |
Any update on this? I see it is still gathering interest. Are you aware of any workarounds or add-ons that can clone an item with its remote links? If you have a procedure or policy document in confluence that is linked to a work item that is repeated, which we do, this seems like a no-brainer use case that would merit the development of the feature.
I'd be happy to put up the code for this with a bit of guidance. +1 vote from me and my teams