Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Change Status of Issue Cloned into Different Project with Jira Automation

When the label "testing-required" is added to any ticket across multiple projects, I have Jira automation set up to clone that ticket into a Kanban board for our QA team.  The automation also makes some transformations to fields for our QA team. 

This automation works great, but the tickets are always cloned into the QA team Kanban backlog.  The QA has asked if it is possible to have the cloned issues placed in our Triage status.  For the life of me, I cannot figure out how to do this.  

When I add a Change Issue Status action to the original automation, I get an error.  I am pretty sure this is because it is trying to change the status of the original issue and not the cloned issue.

Also, when I try a separate automation event in the QA board that runs when a new issue is created and has a label of "testing-required", but this event is never triggered.  It makes it seem like a cloned issue does not trigger a Issue Created event.

Does anyone have any experience with this kind of issue?

1 answer

1 accepted

1 vote
Answer accepted
Alexis Robert Community Leader Jun 02, 2021

Hi @Michael McGory , 

 

I think this is because you need a "Branch" action to change the cloned issue status. Can you try something like this : 

 

Screenshot 2021-06-02 at 11.18.34.png

 

 

Let me know if this helps, 

 

--Alexis

This worked perfectly!  Thank you so much for your help.  I would hug you and buy you a cup of coffee if we met in person hahahaha.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

323 views 9 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you