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

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.

      Am I making wrong assumptions ?

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

            Sorin Sbarnea added a comment -

            Yes, still reproduces 5.2.7

            Sorin Sbarnea added a comment - Yes, still reproduces 5.2.7

            Sorin Sbarnea added a comment -

            just cloning this bug proves this please allow us to reopen closed bugs, otherwise you will endup with lots of clones...

            Sorin Sbarnea added a comment - just cloning this bug proves this please allow us to reopen closed bugs, otherwise you will endup with lots of clones...

            Matheus Fernandes added a comment -

            This behavior seems to still be happening in JIRA 5.

            Matheus Fernandes added a comment - This behavior seems to still be happening in JIRA 5.

            Eric Dangoor added a comment -

            We are running JIRA 4.3.3 but I am still seeing this behaviour. Our installation was upgraded from an earlier release (3.x ?) so perhaps something was done incorrectly ? How can I rectify the problem ?

            Eric Dangoor added a comment - We are running JIRA 4.3.3 but I am still seeing this behaviour. Our installation was upgraded from an earlier release (3.x ?) so perhaps something was done incorrectly ? How can I rectify the problem ?

            Peter Leschev added a comment -

            No problem at all!

            Cheers,
            Peter

            Peter Leschev added a comment - No problem at all! Cheers, Peter

            Grégory Joseph added a comment -

            Ha, excellent ! Looking forward for an update; sorry for the noise.

            Grégory Joseph added a comment - Ha, excellent ! Looking forward for an update; sorry for the noise.

            Peter Leschev added a comment -

            Hi Gregory,

            I have just tried this against 4.2.2. The behaviour is now:

            X-1 has "This issue was cloned as:"
            X-2 has "This issue is derived from:"

            See TST-24391 & TST-24392

            Cheers,
            Peter

            Peter Leschev added a comment - Hi Gregory, I have just tried this against 4.2.2. The behaviour is now: X-1 has "This issue was cloned as:" X-2 has "This issue is derived from:" See TST-24391 & TST-24392 Cheers, Peter

              Unassigned Unassigned
              6b4b1b72e35c Grégory Joseph
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: