-
Suggestion
-
Resolution: Won't Fix
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
The out of the box names for the CLONE link type are "clones" / "is cloned by", which implies an ongoing relationship between the source issue and the clone. It causes a lot of confusion with our new (and old) employees who make not unreasonable assumptions, such as workflow transitions on an issue are applied to any issues that clone it.
The normal use case for the clone functionality is to speed up the creation of an issue that is substantially similar to another issue and then only have to edit the fields that differ, and the relationship between the issues is about something that happened historically. It's still useful to maintain the information for hunting down issues that were unreasonably duplicated.
I suggest that using past tense ("cloned" / "was cloned by") would be more appropriately descriptive. I even find "clone" to be a misleading term for what it describes, and something like "templated" / "was templated from" might be even better.
It's not clear to me if administrators can even do this themselves. (See JRA-13976 and JRA-11600) In any event CLONES is clearly more difficult to change than the other link types and changing it yourself is not recommended.
- is related to
-
- Closed
Hi everyone,
Thank you for bringing this suggestion to our attention.
As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Hi everyone,
Thank you for bringing this suggestion to our attention.
As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.
While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.
Thank you again for providing valuable feedback to our team!