FAQs
Q: If I create a new report by writing a new query, does it get saved as a new filter as well?
A: No. The ability to create, edit, or delete filters resides entirely within Jira. Linked Issue Dependency Mapper allows users to either select an existing Jira filter or enter a custom JQL query to generate a report. However, any custom query entered within the app is not saved as a Jira filter and will not be available for future reference unless manually saved in Jira itself.
Q: How many tickets appear on the dependency tracker page?
A: By default, 1o tickets are shown on the page. However, a user can change it to 20 tickets per page or 50 tickets per page.
Q: How much time does export take?
A: The export duration depends on the number of primary tickets and the number of associated blocker tickets. Depending on the volume, the export process may take anywhere from 10 seconds to up to 5 minutes.
Important: Please avoid refreshing the page while an export is in progress, as this may interrupt the operation and require it to be restarted.
Q: In export, how many levels of blockers appear in the report?
A: By default, only the first-level blockers are displayed with detailed information in the report view.
For example:
Ticket 101 is blocked by Ticket 501
Ticket 501 is further blocked by Ticket 901
In this scenario:
Ticket 501 is the first-level blocker for Ticket 101
Ticket 901 is the second-level blocker for Ticket 101, but the report will not show its details unless Ticket 501 is manually expanded
Note: While Ticket 901 is the second-level blocker for Ticket 101, it is the first-level blocker for Ticket 501.
Q: Can we remove the Blocked By/Blocks/Comment column from the screen?
A: No, they are mandatory columns.
Q: Is there a way to expand all blocker tickets in one go?
A: Yes, by clicking on the 'Expand' icon.
Q: Can I add more columns to an existing report or change the report parameters like linked issues or checkboxes?
A: Yes. To update a saved report:
Open the report.
Make the necessary changes (e.g., modify filters, columns, or layout).
Click the Save icon to preserve the updated configuration.
Q: Can I change a public report to private or vice versa?
A: Yes. To update the visibility setting of a saved report:
Click the edit icon next to the report name.
Choose the desired visibility option:
Private – visible only to you.
Public – accessible to other users in your Jira instance.
Save the changes.
Noted: A user can only modify a report that was created (Private or Public) by them.
Q: Is there a limit to the number of reports I can configure?
A: There is no limitation from our side.
Q: Can we add more “Linked Issues”?
A: No. Linked Issue Dependency Mapper is purpose-built to focus exclusively on the “Is Blocked By” and “Blocks” relationships in Jira. Other link types, such as “Relates To,” “Clones,” or “Duplicates,” are not currently supported within this plugin.
Q: There is a particular filter that I am unable to see in the filter dropdown menu. What could be the reason behind it?
A: This typically occurs when you do not have the required permissions to access that filter.
Filters that are not shared with you (or your group/project) will not appear in the selection list within the app. To resolve this, please contact the filter owner or your Jira administrator to request access.
Once appropriate permissions are granted, the filter will appear in the drop-down menu.
Q: If I am part of Team A, which has a few tickets blocked by Team B and I do not have access to the project Team B, would I still be able to view Team B’s tickets?
A: No. In order to view tickets from another project (e.g., Team B), you must have at least 'View Only' access to that project in Jira.
If access is restricted, the blocker tickets will not appear in your report. To gain visibility, please contact your program manager or IT administrator to request the necessary project permissions.
Jira permissions control all underlying data access, including what's visible in this app.
Q: Are my reports saved permanently?
A: No. Reports that have not been accessed in the past 90 days are automatically deleted.
This retention policy helps maintain a clean and efficient workspace by removing inactive or unused reports, including those created by users who are no longer part of the organization.
To retain a report, simply open or use it periodically to reset the 90-day timer.