Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

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.

Atlassian Community about banner
4,465,122
Community Members
 
Community Events
176
Community Groups

How to search based on initial values of a custom field?

I would like to know if we can search based on an initial value of a custom field?

For ex. there is a custom field called Severity. I would like to search for all the issues that were raised at Severity 1 and later got downgraded to Severity 2 or 3.

I know "changed to" can be used for default fields, but the same does not work for custom fields.

2 answers

0 votes
yuliia_b__SaaSJet_ Marketplace Partner Dec 09, 2022

Hi @First Last 

For custom fields, you can try to find changes with Issue History for Jira app. My team has developed it as a diary for all past activities. It's not like searching with JQL, but you can include any custom field into the grid and see if there were any changes for it for any date range.

columns menu issue history.png

There is a 30-day free trial, so at least, you can check if it can help.

Hello Yuliia,

There are restrictions in place that does not allow me to try this trial! Thanks anyways for providing info.

Hello @First Last ,

Perhaps you can consider using the WAS operator:-

  • severity WAS "Severity 1"

With that said, this operator also returns Jira issues which currently have the value and you may need to filter those out.

Hope this helps.

Regards.

Hello Adrien,

It did not help! Severity being a custom field, history search does not seem to be supported. Here is the error I received:

"History searches do not support the 'Severity' field."

Suggest an answer

Log in or Sign up to answer