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,463,032
Community Members
 
Community Events
176
Community Groups

Jira Migration Assistant - Couldn't import workflow: Resolution -1

Was doing some test migrations from Jira Server 8.5.1 and had some projects import fine but others are failing with this message.

2020-07-21 16:00:14.774 ERROR SBX project-import We couldn't import Workflow 'SCT: RepairQ Workflow' because of 1 missing dependencies: Resolution -1. This caused 133 other items to fail. Check the reasons for the missing dependencies on your server site.

I haven't been able to find anything mentioning this Resolution -1 anywhere.  I checked the Resolutions in Issue Attributes and they all match and seemed the only obvious thing.  Does anyone have any information on what this error is referring to?

1 answer

1 accepted

2 votes
Answer accepted
Tom Lister Community Leader Jul 21, 2020

Hi @David Lewis 

a does your workflow set a resolution in a post function?

check if it uses a resolution value which is not in the target system.

Tom

Thank you so much...you were right.  For some reason we had the resolution being set in a post function to -1 when a ticket was reopened.  Not sure where that came from but created a new resolution for Reopened and set it to that in the post function and was able to import successfully.

Like # people like this

Hi @David Lewis 

that helped me - we also had the problem and did not think of it

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events