BlueGrove Labs markBlueGrove Labs
CTRL K

Support

Contact BlueGrove Labs for StatusPath Reports support.

Vendor

BlueGrove Labs

Support channels

Before contacting support

Include enough context for the support team to reproduce or understand the issue.

Useful information:

  • Jira Cloud site type and app version if available.
  • Module: Main report page, Issue Activity, or Dashboard Gadget.
  • Report type.
  • Work item scope type: Project, Saved filter, JQL, Sprint, or Epic.
  • Work item date range and date field.
  • Trim History setting.
  • Duration Format and Work schedule.
  • Whether you were using Table view, Chart view, export, Columns Manager, saved reports, or gadget setup.
  • What you expected to happen.
  • What actually happened.
  • Any visible error message.
  • A screenshot if it does not contain sensitive Jira data.

Avoid sending confidential work item content, customer information, or sensitive queries unless BlueGrove Labs asks for it through an approved support process.

Bug reports

For a bug report, include:

  • Steps to reproduce the issue.
  • The smallest report setup that shows the issue.
  • Whether the same work item or scope works in Jira directly.
  • Whether the problem happens for one user or multiple users.
  • Whether refreshing or rerunning the report changes the result.
  • Any recent change to Jira permissions, workflow, filters, dashboard sharing, or app configuration.

Feature requests

For a feature request, include:

  • The workflow you are trying to support.
  • The question you want the report to answer.
  • The report type or module where you expect to use it.
  • How often your team would use it.
  • Whether this is for the main report page, Issue Activity, Dashboard Gadget, export, charts, saved reports, or permissions.

Feature requests are reviewed as product input. Sending a request does not mean the feature is committed for a specific release.

Data privacy note

Support may need configuration details to troubleshoot a report, but you should avoid sending sensitive Jira data unless requested through an approved support path.

If a screenshot is needed, remove or blur confidential summaries, names, comments, and any information your organization does not want shared.