Specific Filter of Issue type connected to capabilities

Question

Dear Community,

I would like to create a dedicated filter that is able to connect the issue type and uses lables e.g. :

issuetype in ("Anomalie DS", Bug) AND status in (Open, "In Progress", Reopened, "To Do", Blocked, Funnel, Refinement, Ready, "Sprint included", Implementation, Frozen, "Business Analysis", "Business Review", Testing, "Information Needed", "Analyse d'impact", "Under Qualification", "Clarification Needed", "OOTB Item", Pending) AND labels in (BT_CS, Testability)

but also shows the relation to a certain capabaility, this I woul like to be displayed in a table:

T3DXPOP - 8083   ;   Open Cots and Bugs (filter needs to include only one Capability)  ;   Diagram.

Thank you in advance for your help and advice. Kind Regards Jan

Trudy P Claspill · Answer

Hello @Jan-Christopher Lietsche

Based on the image you provided, is the highlighted issue the Capability? And is the issue that is being viewed in that image a Bug that has been linked to the Capability?

If you are using generic issue linking (the linking that is shown in that image) the reporting capabilities are limited with only native Jira features.

If you have a single issue (i.e. the Capability) and you want to get a report of issues linked to it you can do that with the linkedIssues() function.

https://support.atlassian.com/jira-software-cloud/docs/jql-functions/#linkedIssues--

If the highlighted issue T3DEXPOP-8083 is the Capability you can retrieve all issues linked to it thus:

issue in linkedIssues(T3DEXPOP-8083)

If you want only the Bugs that are linked to that Capability:

issue in linkedIssues(T3DEXPOP-8083) and issueType=Bug

If you want only the Bugs that are linked to that Capability, where the link to the bug is "is blocked by":

issue in linkedIssues(T3DEXPOP-8083,"is blocked by") and issueType=Bug

The limitation on that function is you can get linked issues for only one specific issue at a time.

There is no native filter function that will let you get linked issues for a list of issues. That would require a third party app that extends the capabilities of filtering.

Alternatives:

You could write a program that uses the Jira REST API to make multiple API calls, one to execute the search for each issue for which you want to get the linked issues.

If you have sufficient permissions, you could also consider creating an Automation Rule that would run on a schedule to get a list of the issues for which you want linked issues, and then execute steps in the automation to get the linked issues for each of those issues and send yourself the output via email.

Jan-Christopher Lietsche · Answer

Many thanks for your answer @Trudy P Claspill ,

that is exactly the point, the Cots or Bug have to be linked but which kind of filter command can I use to only show bugs with a certail capability? What kind of filter can I use to include the Capa and what is the best way to link it to each other.

The Capa is set to done but we still have issues open, the bugs appeared after the Capa was tested and set to done!

Trudy P Claspill · Answer

Hello @Jan-Christopher Lietsche

Welcome to the Atlassian community.

How are the Anomalie DS and Bug issue types related to the Capability? Is Capability another issue type? Are the first two direct child issues of the Capability, or generically linked to the Capability?