• Community
  • Products
  • Jira
  • Questions
  • If moving tickets to a new project, what are constraints around using the same fields or adding new fields – will we have to modify every ticket or can we bulk update?

If moving tickets to a new project, what are constraints around using the same fields or adding new fields – will we have to modify every ticket or can we bulk update?

If moving tickets to a new project, what are constraints around using the same fields or adding new fields – will we have to modify every ticket or can we bulk update?

1 answer

Hi,

this is heavily depending on your configuration. Apart from having the nessecary right to move issues, all mandatory fields will be asked for during the move. If there are different fields for different issue types, you will have to move them in groups. If there are any other fields in those issues you want to change you can either do this by editing the issues (after the move) or via bulk change (also after the move).

As you noted allready, bulk change should not be a problem, provided you do have sufficient righs to do so.

Please let me know if that answers your question.

Regards, David

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

26,338 views 2 7
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you