-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
None
-
2
-
4
-
Problem Definition
As mentioned in https://jira.atlassian.com/browse/JSWSERVER-13625, the "Create Linked Issue" does not have an option not to copy Agile data. Beside the option not to copy all the Agile data, the user would also like an option to choose which field values that they can copy. For example, the user would like the option to choose which Sprint values that the new issue should contain. This is important since creating a new issue which is associated to completed Sprint is cause inconsistency in the report.
Suggested Solution
Add option during issue creation using "Create Linked Issue" so the user can choose which field values that should be retained.
Workaround
Create issue manually and link the issue
[JSWSERVER-15870] Allow customizable field copying for Linked Issues when using "Create Linked Issue"
Need option to turn off "Create Linked Issue" duplication of Summary and Description. We like the "Create Linked Issue" but users want to turn off the auto-population of Summary and Description text. Their summary and description is different from that of the Epic and the duplication causes is confusion. I'm sure it is nice feature for some, but we want the option to turn off the duplication. I not seen any options to do this in the documentation, blogs or Jira Admin.
10/19/23 It seems even worse now (9.10) - to the point that users no longer want to use it. It used to auto-populate only a few fields, but now it is many. That mean users have to delete the content in many fields in order to avoid wrong information in their issue. Examples: wrong Sprint, wrong Label, wrong relationship, wrong custom fields, ... Please have a way to turn of the automated population. This isn't used to clone, it is used to create many child issue for an issue (e.g., for an Epic). Duplicating the fields is usually not help and just adds work and errors.
We are running on JIRA Software 7.3.3 and need this feature.
As in our daily work business tickets are created via "Create Linked Issue" functionality.
The root ticket may be part of several sprints, due to our JIRA usage. Some of them may be closed.
"Create Linked Issue" now creates a new ticket in the desired project and when this project has the sprint field in usage will fill the data into it.
So no matter whether the sprint has been closed 5 weeks/day/month ago, it is closed and gets edited with false data.
We need the option this feature is intended to provide to not any longer modify closed sprints and get rid of the workaround which costs a lot of time.
regards,
Ricardo Jimenez Tuero
The "create linked issue" should NOT copy the completed sprints. The created linked issues should function similar to cloning issues and give the user choices.