Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-39639

Rename out-of-box link type "is cloned by" to past tense

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Won't Do
    • None
    • Issue - Actions
    • None
    • 1
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? 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.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              9e38ab35829a Ert Dredge
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: