RELATED IDEAS
Limit report list by dependency links
As a central organization delivering many capabilities across many of our products, I need to be able to create a report that shows all of the dependencies for that program on my team, but I can't because there is not a way to put a "where clause" in the reporting.
Assume a product called X. It has dependencies on 100 features across 20 products. I want to say, show me all of the features in product X where there is a dependency link to Product A, B or C only.
I have created a report that shows all of the features and their dependencies, but I see a lot of features that I don't care about because they are not dependent on products I care about.
Ideally, I'd love capability like there is in Jira where I can create custom JQL to do what I want, but would be happy with some way to filter or otherwise int he existing interface
Todd Meyer in support asked me to enter this.
| Release time frame | 3 months |
-
ADMIN RESPONSEApr 28, 2023
You can now include key details about dependent work items — like the status, assignee, and due date — in reports and custom roadmaps to help keep your plans on track.
This update includes the ability to filter by record link relationship type:
© 2024 Aha! Labs Inc.•All rights reserved
This capability is definitely needed. The requirement for this organisation is to be able to create a report which shows one product and all the epics which are dependent upon epics from another product. The end result being an automated report of the risks to the product.
The second aspect is to create a report which shows all blocked epics dependent upon epics outside of their product. The end result being an automated report of the issues to the product.
I have raised a separate idea for linking of records to be possible at requirement (stories for this organisation). When this is delivered, the capability to report risks and issues at requirement level will also be needed.
This might make or break Aha! for us. We need to be able to create a report that shows dependencies across our services/solutions.