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,466,735
Community Members
 
Community Events
176
Community Groups

Migration of tickets

Hi admins!

How do I bulk migrate Jira Service Management Tickets to a  Jira Software backlog board?

Will I have to do this via a rule?

2 answers

Hi @Vanessa Becker

Search for all the items you want to move to the software project and then execute a bulk move action.

Take into account that if you want to retain all information in regards to fields , issue types or statuses, you will have to have the identical workflow, issue type and screen schemes on the Jira Software project.

The values of the custom fields will till be retained in the fields but then they are not visible on the Jira Software project until you add the desired fields to the screens of the Software project.

Data related to Component and Version will be lost as they are project bound.

If not, then on moving you will need to specify the new issue type, status. 

You can find more information here: Migrating issues

Best regards,

Marc

I guess there are no components or versions in JSM projects. Also the info to custom fields visibility is a kind of irrelevant here.

Also there is no need to make same statuses - they can be mapped to Jira Software project statuses on the last step of bulk move.

Anyway if it is one-off operation (e.g. boss told to close portal and use Jira Software) - it is a good solution. If it is just the case of adding tasks to developers using portal - I am 100% sure it should be done using a rule that will keep original request in place and create a copy in developers project. There are many pros of having a JSM for customers (e.g. for not paying for licenses) and having Jira Software for developers. My opinion is that only L2/L3 support should be agents in JSM.

Like Guy Thorsby likes this

If you mean moving issues from Service Desk project to Software project, you can do it by Bulk Move.

Find all issues in Search, select ... and then Bulk change.

 

But you will need corresponding permission for both projects.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events