The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Change reference ID to cloned issue

Dextall UAB
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 11, 2024

Hello,

 

I wonder if it is possible to change the customer's reference ID.

For example, we have a ticket system where customers can create tickets.

The customer creates a ticket and gets a reference ID: SD23. Let's say the issue is within the developer's scope, so we clone (automate) that ticket and copy it to the developer's board. After that, we would like to assign a new reference ID so the client can see comments and status from the other board. 

If this is not possible, maybe there is a workaround since moving tickets to another board is not allowed by automation.

Thanks.

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Answer accepted
Lígia Zanchet
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 13, 2024

Hello Dextall

Welcome to our community! 

Based on your description, you are cloning the issues and want a reference ID for the users.

There are a few possibilities here.
As you are using automation to clone the issue, it would also be possible to add a comment to the trigger issue with the new issue created:

Just use the smartvalue {{createdIssues}} and re-fretch issue data as per the example:
Screenshot 2024-06-13 at 14.32.32.png

 


Now, "If this is not possible, maybe there is a workaround since moving tickets to another board is not allowed by automation."

I'm unsure if I understood this part correctly, but let me explain the concept of boards.

Boards are visual representations of filters if you have one board A with the filter:
project=ABC and type = Bug
The only issues that will appear on that board are the ones that match both conditions of the filter.

And you have a second board B
project=FGH and type = Bug

If you need to move the issue from Board A to Board B, you would just need to move the issue from one project to another. 
That way the issue would match board B and unmatch conditions from board A.

Please let me know if that information was helpful or if I misunderstood your statement I'll be happy to assist you further. 

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events