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

The "cloner" relationship is inverted

XMLWordPrintable

      When I clone issue X-1, a new issue X-2 gets created.

      I expect the relation ship to say "X-1 is cloned by X-2", and "X-2 clones X-1" (i.e "the new issue is a clone of the older issue"), but Jira creates the relationship in the other direction.

      Having installed JIRA (v4.4.2#662-r164433), I still have the same problem. First installed version was as far as I remember 3.13. Then upgrades have been made.

        1. Cloned Issue.png
          Cloned Issue.png
          44 kB
        2. Issue.png
          Issue.png
          44 kB

            [JRASERVER-25983] The "cloner" relationship is inverted

            Łukasz Indeka added a comment - - edited

            It looks like it was fixed for new installations but not for upgraded ones.

            I have never seen JIRA from the database perspective, but I think that best solution is to invert the link names (like Eric suggested) and then fix old links. For the fix we could quite safely assume that issue with greater id/key clones the one with lower id/key.

            Łukasz Indeka added a comment - - edited It looks like it was fixed for new installations but not for upgraded ones. I have never seen JIRA from the database perspective, but I think that best solution is to invert the link names (like Eric suggested) and then fix old links. For the fix we could quite safely assume that issue with greater id/key clones the one with lower id/key.

            Matheus Fernandes added a comment -

            This behavior seems to still be happening in JIRA 5. (see the attached screenshots)

            Matheus Fernandes added a comment - This behavior seems to still be happening in JIRA 5. ( see the attached screenshots )

            Eric Dangoor added a comment -

            We have the same problem (we are now on 4.3.3).

            One way around the problem is to invert the link names in the Cloners link type definition. However, this would automatically invert all existing links, including any that had been created using the Link operation rather than the Clone operation. Since those are likely to be in the correct direction they will now become incorrect.

            Another solution is to create a new link type with a different name but perhaps with the same inward and outward names, and associate he new link type with the Clone operation(in atlassian-jira.properties). However this is messy as the will be 2 virtually identical link types as options in the Link operation.

            Eric Dangoor added a comment - We have the same problem (we are now on 4.3.3). One way around the problem is to invert the link names in the Cloners link type definition. However, this would automatically invert all existing links, including any that had been created using the Link operation rather than the Clone operation. Since those are likely to be in the correct direction they will now become incorrect. Another solution is to create a new link type with a different name but perhaps with the same inward and outward names, and associate he new link type with the Clone operation(in atlassian-jira.properties). However this is messy as the will be 2 virtually identical link types as options in the Link operation.

              Unassigned Unassigned
              106a1e9af0d0 Łukasz Indeka
              Affected customers:
              0 This affects my team
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: