Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Bug Filtering - Report on Defect's Highest Environment by Excluding Lower Environments

Calum Mitchell
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 9, 2025

Hello Atlassian Community,

 

I've been tasked with editing some filters and am particularly struggling with the below requests to report on a defect's highest known environment only by excluding the lower environments (where applicable):

  • If PROD defect is also in UAT & SIT, exclude UAT & SIT to only report PROD
  • If SIT defect is also in UAT, exclude SIT to only report UAT

Any assistance would be greatly appreciated, thank you! 

1 answer

0 votes
Mercy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
December 10, 2025

Jira’s native JQL can’t “rank” values within a field and automatically suppress lower-priority matches, so to report only the highest environment for each defect you’ll need either a calculated field or automation to capture that logic before filtering. A common approach is to add a custom single-select field such as **Highest Environment** and use an [automation rule](https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/) triggered when the Environment field changes to set this to the highest applicable value based on your hierarchy (e.g. PROD > UAT > SIT).

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events