Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
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

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,560,125
Community Members
 
Community Events
185
Community Groups

Field info not preserved when moving tickets between projects that have differing field schemes

Edited
Raj Vora
Raj Vora Oct 06, 2022

When you move a ticket from Project A to Project B where Project A has a field (let's call it "Solution") that Project B does not:

Does the the information in the "Solution" field get preserved in Project B and if so, where does one find this?  I've looked in the activity and history log of the ticket (migrated to Project B) and can't locate it.

Answer
Watch
Like Be the first to like this
178 views

1 answer

0 votes
Nic Brough -Adaptavist-
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Become a leader
Oct 06, 2022

How can it preserve it?  You haven't got anywhere to keep it in the new issuetype/project.

But, what actually matters here is the underlying data - if a field is hidden, or not on screen, then you don't actually lose it, you just can't see it.  It only gets deleted if you move to an issuetype for which the field does not exist at all (and that goes into the history)

To see the field in the new location, un-hide it or put it back on screen (or both)

Reply

Suggest an answer

Log in or Sign up to answer
Jira Core
Jira Core Server
TAGS
AUG Leaders

Atlassian Community Events

See all events