You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I moved some issues from Project 1 to Project 2 without realizing that the "Acceptance Criteria" field in Project 1 wasn't present in Project 2, so my Acceptance Criteria was lost.
Is there any way for me to restore the content from the Acceptance Criteria field, either by reverting the issues to the original project or some other way?
Hello Chris,
If the Acceptance Criteria field context was global, the values are still on the database, you just need to add the field to the project 2 screen in order to see its values. You may first check the field context, if it is limited to certain projects only, add project 2 on the list, and then add the field to the project 2 screens.
Hope it hels,
Best regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the community!
I'm not entirely sure whether there is a way of restoring the field - but I will provide a potential workaround for you.
If you add the field to Project 2, you can then use bulk change to update the field for all the issues. You'll need to do it once per Criteria, so could take a while depending on how many options you have.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Wow - ok, I just found out that in a JSM project, it's not sufficient to just have the correct issue type, but you also need to select the appropriate request type that matches the fields on the original request, otherwise they still dont show.
There's also the ... > Find your field tool that can help figure out whats going on!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.