I'm trying to transfer all issues with type "task" to type "story" by deleting type "task".
But I have receiving a following error:
At the same time I have no errors in another project.
What differences I have to get rid of?
Differences in field configurations and workflow will cause this warning. Screens may also be a problem for you, but they won't block the move like this (your people will soon tell you if the screens are broken after the change)
Best thing to do is to try making the change manually - pick an issue that is of a task type now, and try using "move" to change it to the new type. This will tell you about all the changes that are needed for migration so you can go back and line-up the configs between old and new type by hand, or what to expect if you use bulk-edit to change many issues at the same time.
@Nic Brough -Adaptavist- Thank you for your answer.
It is a team-managed project.
All settings (workflow, screens) for both of types are the same.
If I manually change type from task to story - I have no any warnings.
Where I have to make changes?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Not familiar with team project but in company I do a bulk move from task to story, then follow-up with deleting the type task.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, that suggests you chose an issue that doesn't have any data that needed migration. Next step would be to use bulk-edit to try changing a swathe of them from one type to another - try the first 50ish maybe?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Nic Brough -Adaptavist- @Del Jensen thanks a lot!
All issues have been transferred without any problems with a bulk move.
But I still don't understand why my first way doesn't work )
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.