Support

Support for Dependency Radar is primarily provided through product documentation, including installation guidance, user guidance, configuration notes, and troubleshooting information.

Customers may raise support requests for suspected app defects, installation issues, configuration questions, or unclear product behaviour. Customers may also submit enhancement requests for future consideration, including improvements to saved views, reporting, Matrix view, Sprint view, risk presentation, configuration options, or Marketplace documentation.

Dependency Radar is a presentation layer over the customer's underlying Jira data. It reads existing Jira projects, issues, issue links, statuses, dates, and configured app settings, then presents that information as Sprint and Matrix dependency views. The app does not create, edit, correct, or own the customer's Jira dependency data.

The customer is responsible for the accuracy and maintenance of their Jira data, including issue links, project structure, workflows, statuses, dates, permissions, and dependency conventions. If dependencies are missing, linked in the wrong direction, mapped to the wrong project, or based on incomplete Jira fields, those issues must be corrected in Jira or in the customer's app configuration.

Support can help identify whether a problem is likely caused by app behaviour, configuration, or underlying Jira data, but responsibility for customer data quality remains with the client.