Hi All,
A user has reported an issue with clone tickets.
TEST-11684 is a clone ticket of TEST-11034. On the following board ( Attached screenshot for your reference ) TEST-11684 should fall into the "Clones" Swimlane. However, it is falling into the "New Queries" Swimlane instead.
Can you tell me why this is happening pls ?
Also on the board it's showing only "Reopened Queries" and "New Queries" Swimlanes rest of the two Swimlanes not showing.
Hi @Roja Gurram
For swimlanes not appearing - only swimlanes with at least one issue matching the JQL will appear on the board. When a swimlane is empty, it's not visible on the board.
For the clones swimlane - have you checked the cloned issues are receiving that link type?
It is possible to remove the link type entirely from Jira or disable the auto-linking using a script - or, it might have been manually removed by a user.
The JQL looks fine so these are possible scenarios it's worth checking for. Just to verify though, if you search for this JQL (within the parameters of the board filter) in the issue search, what does it return?
Ste
1) For swimlanes not appearing - only swimlanes with at least one issue matching the JQL will appear on the board. When a swimlane is empty, it's not visible on the board. -
Ok, Thanks for the clarification.
2) For the clones swimlane - have you checked the cloned issues are receiving that link type ? -
I have checked it on the Issue links it's showing" Related to " instead of "Clones". Attached screenshot for your reference. Please let me know if that's wrong.
3) It is possible to remove the link type entirely from Jira or disable the auto-linking using a script - or, it might have been manually removed by a user. -
YES, We can remove the link type Manually in Jira. Attached screenshot for your reference. My question is if we remove the link type "CLONERS" in JIRA User's cannot able to clone issues right.
4) The JQL looks fine so these are possible scenarios it's worth checking for. Just to verify though, if you search for this JQL (within the parameters of the board filter) in the issue search, what does it return? -
Ok, With in the parameters i have given the board filter it shows the same as previous issues ( Lists the number of issues ).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Roja Gurram
The issue here appears to be the link type in the issue - if it is listed as "relates to" and not "clones" - then it won't come up in your swimlane as it doesn't meet the JQL parameters.
To check if this is automated or manual, check the issue history and see if a user has manually removed clones / added relates to - or if the link type was set automatically during creation.
If it was automatic, you could just change your JQL to search for "relates to" as opposed to "clones" - although this might bring up non-cloned issues also if it's a link type which is used more generally.
Your alternative is to look into what is causing the auto-change in link type - as it could be a range of reasons, I'd probably start by asking within your Jira Administration team :)
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Stephen,
Thank you for the prompt response.
I am the Jira Admin, I will check and get back to you with the update on this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Stephen,
1) To check if this is automated or manual, check the issue history and see if a user has manually removed clones / added relates to - or if the link type was set automatically during creation. -
I have checked in issue history user has not changed the LINK TYPE manually.
2) Your alternative is to look into what is causing the auto-change in link type - as it could be a range of reasons, I'd probably start by asking within your Jira Administration team :) -
How can i check the Auto Link type pls ? However, i have seen "Linked Issues" Custom Field is not present on the SCREENS like create, Edit, view.
Please suggest me accordingly i think "Link Type " is automatic but not sure how i need to check the Link type is automatic or manual.
Looking forward to hear from you again!!!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Roja Gurram
You'd need to look in your instance for scripts, automation rules, groovy scripts, etc - that might be running (either on the platform, via workflow create post-functions, on apps or similar).
One further thing you could check is whether the link type "cloners" has been modified to be "related to" as opposed to "clones":
If it has, you could change it back - or simply modify your filter from "clones" to "related to"
If it hasn't been changed, check where "related to" falls under from a link type perspective.
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Stephen,
I don't think "Link Type" has changed. Attached snippet for your reference.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Stephen,
Can you please assist me on this issue your help is hughely needed.
Thanks a lot for your support till now.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Roja Gurram
Perhaps a next step would be to check if "Reference" is the link type used during a clone.
Clone an issue from your board and see what link type is used immediately after creation. If it is "clones", you can also refresh 10-15 seconds later and see if it changes at all (automation rules run just after creation).
If it is "related to" at creation - or it changes soon after - that's when I would start looking into scripts, automation rules, workflow post-functions and similar.
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Stephene,
I have created test tickets and did the cloning also in ISSUE LINKS it's showing as "Clones" only. Attached screen grab for your reference.
1) Clone an issue from your board and see what link type is used immediately after creation. If it is "clones", you can also refresh 10-15 seconds later and see if it changes at all (automation rules run just after creation). -
Link type showing as "CLONES". Not changed anything after doing refresh.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Roja Gurram
Did this issue appear in the swimlane on your board?
This result points to:
I'd look into (1) and (2) first - if cloning is working as expected these are the two most likely scenarios. If you want to look into (3) to make sure, you'll need to do that investigation within your settings.
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Stephen,
Thanks a lot for providing the clear information on this.
Did this issue appear in the swimlane on your board? - Yes, appeared under the swimlane in the board.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Stephen,
One dumb question please.
Is it possible to clone a new JIRA ticket from an existing one?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Roja Gurram
You can clone an issue from an existing one:
^ Is this what you're looking for?
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Stephene,
Thank you for the response and solution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.