-
Bug
-
Resolution: Fixed
-
Low
-
None
NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.
If you clone a ticket, the link that's placed on the ticket reverses the outward and inward descriptions. So, the reference will refer to the clone as the original and the original as the clone.
This has been confirmed on my test instance, did not happen in OD-1, but does in OD-6.
- is related to
-
JRASERVER-31645 Cloning issues reverses the link comment, calling the original the clone and the clone the original
-
- Closed
-
- relates to
-
JRACLOUD-32042 Link relationship shows "original issue" clones "new issue" when cloning an issue
-
- Closed
-
Cloning issues reverses the link comment, calling the original the clone and the clone the original
-
Bug
-
Resolution: Fixed
-
Low
-
None
NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.
If you clone a ticket, the link that's placed on the ticket reverses the outward and inward descriptions. So, the reference will refer to the clone as the original and the original as the clone.
This has been confirmed on my test instance, did not happen in OD-1, but does in OD-6.
- is related to
-
JRASERVER-31645 Cloning issues reverses the link comment, calling the original the clone and the clone the original
-
- Closed
-
- relates to
-
JRACLOUD-32042 Link relationship shows "original issue" clones "new issue" when cloning an issue
-
- Closed
-