nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Cloned Issues - Unique Identifier

Ramesh Kale

I have a setup where I have cloned the set of issues which carry forwards custom fields when being cloned and transitioned as per the workflow. It works great

Further for reporting and classifying purpose -
I am looking for a unique identifier basis I can segregate the set of tickets which are cloned with same parent.

What and where should I look for such identifier?

Accepted answers

Petter Gonçalves

Hello Ramesh,

Thank you for reaching out.

I understand that you are looking for a field/way to identify all the issues cloned from a specific issue, ordering them in a way that you can clearly see which issues were cloned from the same issue. Is it correct?

By default, all issues the cloned issues are configured with a link to the issues they were cloned from. This link (Clones, Cloned by) can be returned using JQL and can be used to identify all the issues cloned from the same issue:

issue in linkedIssues(ABC-123, clones)

If this is not the feature you are looking for, could you please give us more details on what exactly you are planning to achieve with the unique identifier?

Let us know if this information helps.

All comments

Petter Gonçalves

Hello Ramesh,

Thank you for reaching out.

issue in linkedIssues(ABC-123, clones)

If this is not the feature you are looking for, could you please give us more details on what exactly you are planning to achieve with the unique identifier?

Let us know if this information helps.

Ramesh Kale

Yes, you are correct. I am looking for a field to identify all the issues cloned from a specific issue. So that in the reports i can just filter them out by specific key or value.

I am generating reports using easyBi add-on in JIRA.

As you answered, what query i should run and where? Will that help to generate report and filter out the issues?

>> I was trying to introduce a new custom field with unique value for each parent task which i am creating manually and that unique value field will be cloned for the cloned issues triggered in its post function.

It will save my efforts to filter them out by just value of that unique custom field per task.

However i have to put that value manually every time and i can not track what was the last value i put as there are multiple users who creates the parent tasks.

Also not getting anything to automate it so that the new custom field will become unique each time.

e.g. Numbers in incremental order like 1,2,3,4,....

is there any query or rule where i can achieve this?

Or just we can achieve this by running a query as you mentioned before.

Petter Gonçalves

Hello Ramesh,

I'm not aware of how easyBI reports work, but the query I mentioned will give you all the issues that were cloned from a specific issue you defined:

issue in linkedIssues(ABC-123, clones)

You can run the query above in your issue navigator clicking in the Jira icon ( or ) > Issues and filters > Select Search issues > Switch to JQL, just like described in the documentation below:

Advanced searching

Additionally, I believe you could use an easyBI report based on a JQL query, once you configure the filter you want.

Let me know if you have any questions.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

jira

cloud

bitbucket

bitbucket-cloud

jira-service-desk

jira-service-desk-cloud

jira-cloud

confluence-cloud