Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,467,417
Community Members
 
Community Events
177
Community Groups

How to move jira service management ticket to a another project?

Hi!

I need to automate urgent jsm bugs by moving to the development project.

Is it possible, through automation, to move a jsm ticket to a specific project and board?

 

thank you for your help!

2 answers

2 accepted

3 votes
Answer accepted

I would recommend not doing that.  Issue move is for genuine mistakes and housekeeping, it's not something you should be doing as part of a process.

Between some types of project, it's not so bad, but moving issues out of a JSM project is not a good idea - you lose the request it is associated with, making the customer think you've deleted their request.

"Create development item as a result of a request" is best done by using the "create issue in other project and link" function.  That way, the developers can use their process as normal, the customer still has the request, and the developers can see where it came from and update either end of the link.  Click on the "link issue" icon first, to get the area where links are shown, and look at the bottom of it for the create/link button.

thanks for the tip!
It makes sense.

Thanks

Would people be worried that if the JSM request was built using the new Forms functionality then that data wont carry across and you would have to flick back and forth between the linked issues.

New, so I need more support on this. The suggested solution, does that mean: TRIGGER: new issue, THEN: CLONE - {{issue.summary}} into an other project, AND link to newest issue?

sorry, that was automation. and that was not suggested! I found the way to clone and link within the issue.

1 vote
Answer accepted
Trudy Claspill Community Leader Feb 08, 2022

Hello @Patrícia Gomes 

Welcome to the community.

Jira Automation doesn't currently support moving an issue with a single "move issue" action. You have to clone the issue then delete the original. Refer to 

https://support.atlassian.com/cloud-automation/docs/move-an-issue-to-another-project-using-automation/

As for putting it "on a specific board", a board is just a way to view issues and the board is based on a filter. If the new issue is within the scope of the board filter, then it will show on the board.

thank you for your help!
I'll try it this way

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events