It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Do custom field options reset to default for every project issue once they’re hidden? Edited

I’m doing cleanup as one of our company’s projects have used the wrong field configurations for their issues. I received a complaint from one of our project leads when changes were made to hide a custom field they were using.

In our test environment, I made copies of every configuration they have used and renamed it under their project’s name, enabling the custom field’s visibility as well. However, in doing so, I tried checking the values for those custom fields, and it looks like they’ve been set to their default option, which is “none.” I’m checking as well to see if this is true, but I wanted to seek confirmation from others who might know.

1 answer

1 accepted

0 votes
Answer accepted

Fields are hidden if they are empyt, if you've turned on their visibility they will show "none", but data stored in them already won't be changed. I think after you have changed the visibility, one project lead saw the "none" value and got confused.

So what you’re saying is that the values remain unchanged when you un-hide the custom fields?

Yes, the only question is: did they have any value while they have been hided?

For this one team, it does have value. Still, it’s comforting nothing is lost. They are a QA team and they need the data from these custom fields.

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you