Issue Search: custom fields/property shows default but it should not

[Deleted user]

Hi there, 

We have a custom field/property with a default value set to None. 

Then, whenever we go to advanced issue search/filters the custom field appears on two rows - one with the data added to the field and one below hat with None value. 

Do you think that's an issue and/or it's a matter of Setting we can change/modify. 

Thanks in advance. 

[Isgarcia]

I'm facing the same issue and would like to resolve it, is there a way to remove None from displaying in the grid, @Nic Brough -Adaptavist- do you happen to know?

[John Funk]

Hi Greta,

Is there maybe some automation that is running that is populating the value? If you go into the history of the issue, do you see if the field value has been update and by whom? 

The easiest what to see if there is a default value actually in there is by creating a new issue. In the create screen, if there is a default value, then you should see it. Otherwise, the user is putting in a value before they create it or some type of automation is adding it after the fact. 

[Deleted user]

Hi John, 

No, it's a manual update of this field, we don't have automation for populating it. 

Yes, we can see the history - how it used to be None and then changes with every new update. 

The field is by default None which is not the problem. 

The issue is with searching after that and reviewing filters and advanced search - the column is visible but there are two values -> the None value (the default one) and the one that's being filled by someone manually. 

It's visible on the advanced issue screen screenshot - there are two rows instead of one for this field - Customers - one pre-filled with the manual data and on the second row the None value which looks strange and it's not correct. 

[John Funk]

Ah, I see now. This appears to be a Bug with the list view. It seems to be showing the original value and the new value. I would submit a ticket to Atlassian:

https://support.atlassian.com/contact/#/