Removing prior values of custom field from an issue

[Sonu Bhatia]

I created a custom field (free text format) and entered a value in that field for specific story tickets. However, when I clear that value on some of the tickets and create a filter by that value, it includes the story tickets where that value was previously entered.

How can I hide the tickets where this value no longer exists?

[padraik · Accepted solution]

A few questions:

• is "CMR #[Short text]" ~ CR-03967 the entirety of your JQL query or is there more?
• Does that field CMR #[Short text] contain a lot of text, and you want the filter to pick the issue up if "CR-03967" is in there somewhere?  Or does it only contain the CR-## 
  • If the field ONLY contains the "CR-03967" you could try switching your operator from ~ to =

Tou mentioned "while the 3rd one now shows blank value in the list" so you could also append AND "CMR #[Short text]" is not null
to your query.

[Sonu Bhatia]

Thanks Padraik......adding "CMR #[Short text]" is not null to my existing query worked in hiding the ticket where CMR field was blank. Appreciate your suggestion!!!

[padraik]

Happy to help!

[John Funk]

Hi Sonu - Can you share an example? Because it should definitely not show issues in a filter that that have no value in the field and the filter is based on the field. Can you share the filter? 

[Sonu Bhatia]

Hi John, here is the JQL I used: "CMR #[Short text]" ~ CR-03967

This filter lists 3 Jira ticket.....2 of them still have the CMR # custom field tagged with the value of "CR-03967", while the 3rd one now shows blank value in the list, but is still part of the filter list.

[Sonu Bhatia]

So it seems like once a value is input in this custom field, even if it is removed later, it is still part of that ticket and pulls it up during filter search.

[John Funk]

This sounds like it might be a caching issue with your browser. But let's do this

Run the JQL and include the custom field in the columns displayed. And then do a screenshot and post here. 

[Sonu Bhatia]

Hi John,  here is a screenshot for the query and the search list. 

As you can see, the 2nd issue in this list has no value displayed for the CMR# custom field.