If your custom fields are using contexts, then the values/descriptions of those custom fields are bound to the specific project where that context was created.
Hence other projects could use the same custom field, but have different possible field values, or a different descriptions. But that alone doesn't explain why switching project types would change that.
What project types are you changing between?
The other thought is that this could be a field configuration scheme problem. I am curious to see if the changing of this project would automatically change your field configuration scheme in use here. Those schemes can also control the descriptions that a custom field have on a per project basis. So that seems like the most likely culprit here to me.
Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot