Issue Summary
This is reproducible on Data Center: (yes)
Today, when we have an EPIC (like a template issue) having multiple tasks/subtasks, and each task/subtask, has its rank and its respective order if we clone those tasks/subtasks in a different place, we are not persisting/respecting the rank we have currently configured under those issues.
Even if we organize the JQL output by rank (see step #3 below)
Steps to Reproduce
- Configure an Epic having multiple tasks and subtasks, and place the rank/score in those
- Create automation to be triggered when issue is created
- Configure a branching to retrieve the data from the Epic based on a JQL
issuekey in childIssuesOf("MYEPIC_1") order by rank
- Then create an action clone issue in the same or different project.
- Additional plot to this feature request.
Expected Results
As a Jira admin I would expect that when cloning issues, the application should be forced to persist in the same rank position we see in the original ticket template.
Should be really good if the fix could be implemented in the JQL itself as the user would not be forced to place additional smart values or other things in the automation, making it "SMART" and "CLEAN"
Actual Results
The ranking we have on tasks/subtasks in the original template ticket (the one we are cloning from) is not preserved in the ticket we are cloning into.
Workaround
None
- links to
