Find count of defferals from one version to other

Question

Hi,

I am trying to build jira query which would return number of defects which were opened in one version and they are pushed out to next version. For example, let's say I found 200 issues during current release say "A". While triaging, we though out of these 200 we find 95 defects we would like to fix in next version say Release "B". We update Fix version of these 95 defects to "B".  We call these 95 defects as deferrals from current release (Release "A").

What would be query to determine deferrals which were found in one version but are planned to fixed in different version.

Bill Sheboy · Answer

Thank you for clarifying how your teams are working.

Unfortunately, JQL is not a SQL, and so comparing things like Affects Version and Fix Version does not appear to be possible.  It only allows comparing a field to a constant, literal value.  (Example fixVersion = myVersionA)

For JIRA Cloud, I can think of two possible solution approaches for what you ask:

* Export your data to another tool, like a spreadsheet, and run the query there
* Automation rules are able to compare the values of fields.  So you could build a rule which compares the fields as you have indicated, and then send an email report of the results.

To learn about automation rules, start with this documentation:

https://www.atlassian.com/software/jira/guides/expand-jira/automation

https://support.atlassian.com/jira-software-cloud/docs/automate-your-jira-cloud-processes-and-workflows/

Mihir Gandhi · Answer

Hi @William Sheboy

We rely on "FixVersion" field to determine how many defects were fixed in current release. Affect version tells us where defect originted. Many times, defect get pushed out multiple versions. For ex, a defect originated in version "A" and currently targetted to fix in Version "B". Now during version "B" development, we found that we have lack of resources so we push this defect to version "C".

I can find deferrel if defect's affected versiona and fixversion don't match. But is there a way to know if defect gets pushed out from current version to next version and current version is not affected version?

Bill Sheboy · Answer

Hi @Mihir Gandhi  -- Welcome to the Atlassian Community!

Possible answers to your question depend upon your team's practices today...

How are you tracking the releases which a defect impacts?  For example, are you currently setting the Affects Version field to all Releases which a defect impacts?

How are you defining Release numbers?  Are they defined in a manner where you can easily (and programmatically) determine which was last and which was next?

Best regards,

Bill