How do I find all bugs linked to user stories

[raanan tauber]

We are working CI/CD with Kanban boards and some of our bugs are backlog bugs, and some are linked to user stories.

I want to see how many bugs during a specific time period were handled by the team (i.e. were in statuses of "in development", "ready for testing", "in testing") and also linked to a user story (when of course this is a general query and I don't know the specific user story issue#).

How can I generate such a query?

[Earl McCutcheon]

Hi @raanan tauber ,

To get the issues that were in a specific status during a certain time period you can use a combination of the "status" field referance with the "changed" operator and an "during" optional predicates modifier.

The following Example and a few others can be seen in the following community post that discuss this further, but something like the following looks like it would fit your use case, modifying the query to contain the multiple possible status changes that can occur per your workflow of the noted "in development", "ready for testing", "in testing" statuses:

• https://community.atlassian.com/t5/Jira-questions/How-to-write-a-JQL-to-find-issues-status-changed-on-Last-week/qaq-p/231919

project = "Project Name" AND status changed FROM "Status 1" TO "Status 2" DURING ('yyyy/MM/dd', 'yyyy/MM/dd')

A tip on the status change possibilities would be workflow contingent.  If the workflow can transition only from status 1 to status 2 you only need to do the one changed option; i.e. the workflow is  "open > In Progress > Done" and "open" can only transition to "In Progress" you only need to input the single status transition.  But if it's a global transition i.e. all statuses can be transitioned to the status, or there are multiple transitions possible  you will need to do a "From 'old status' TO 'new status'" for every possible status transition to the desired status; exe:

project = "Project Name" AND (status changed FROM "Status 1" TO "Status 2" DURING ('yyyy/MM/dd', 'yyyy/MM/dd') OR status changed FROM "Status 3" TO "Status 2" DURING ('yyyy/MM/dd', 'yyyy/MM/dd') OR status changed FROM "Status 4" TO "Status 2" DURING ('yyyy/MM/dd', 'yyyy/MM/dd'))

Then modify the JQL to include the Linked issue with a "linkedissue" field referance with an "=" for a single issue or an "IN" for multiple issues for the target issue exe "AND linkedissue = issuekey-1" OR a "linkedissue in (issuekey-1, issuekey-2, etc...)"

For additional details and a full list of the of the JQL avaliable check out the documentation here:

• Advanced searching
  • Advanced searching - functions reference
  • Advanced searching - fields reference
  • Advanced searching - keywords reference
  • Advanced searching - operators reference
  • Advanced searching - developer reference

Regards,
Earl

[raanan tauber]

Hi Earl,

Thanks for the answer. But the issue I'm finding trouble with is finding all the bugs linked to any issue (and not to a specific one). Maybe I didn't specify this enough in the question.

[Earl McCutcheon]

Hi @raanan tauber ,

Thanks for the update and and that would be a different query all together, and while I was looking into this I found a new Bug tied tied to the JQL value that would be related to this search item via the JQL search using "issueLinkType".

 "issueLinkType" only supports the operators "=", "!=", "IN", "NOT IN" as covered in This Documentation for Advanced Searching,  However the options  "IS" & "IS NOT" are also avaliable but are Unsupported operators, and should not be present but would provide the functionality you are looking for here.

Using the currently support functionality I detailed in the workaround section of the Bug a method that can be used to isolate any issue with a link associated, noting that the saved filter you use would need to be modified to include any new issue link types created after the filter is created.

The Bug is viewable here:

• https://jira.atlassian.com/browse/JRACLOUD-73416

And as some follow up on the Bug I reached out to the development team and we are looking at the "IS" & "IS NOT" operators as a feature possibility to add in as part of the fix.

Regards,
Earl