BlueGrove Labs
CTRL K

Permissions and Data

StatusPath Reports respects Jira permissions and uses Jira data needed to calculate reports. The app is built for Jira Cloud Forge and stores configuration required for product features.

Users can only analyze work items they are allowed to view in Jira.

When to use this

Use this page when reviewing data access, preparing Marketplace documentation, answering administrator questions, or investigating why users see different report results.

Before you begin

  • Know which Jira project, filter, sprint, epic, or JQL scope is being used.
  • Confirm the current user’s Jira permissions.
  • Review your organization’s policy for Jira apps and reporting data.

Steps

  1. Confirm the current Jira user.
  2. Confirm the report scope.
  3. Verify that the user can view the included issues in Jira.
  4. Review which issue fields are selected for the report.
  5. Review saved reports, defaults, and recent setup settings if relevant.

Data read for reporting

The app may read:

  • Issue key
  • Summary
  • Status
  • Assignee
  • Project
  • Issue type
  • Created date
  • Updated date
  • Resolved date
  • Changelog history
  • Selected Jira fields required for reports
  • Jira project, filter, board, sprint, status, field, and user lookup data needed for setup controls
  • Dashboard item properties for gadget configuration

Data stored for product features

The app may save:

  • Saved reports
  • Default report settings
  • Recent setup
  • Draft setup
  • User-specific report preferences
  • Admin settings
  • Work calendars
  • Project settings records
  • Dashboard Gadget configuration in Jira dashboard item properties
Permission rule:
If a Jira user cannot view an issue in Jira, the app should not include that issue in reports for that user.

Result

Report output reflects Jira data available to the current user and the configuration stored for report convenience features.

Notes

  • Different users can see different report results if their Jira permissions differ.
  • Saved configurations can restore report settings, but results may change when Jira issue data changes.
  • Do not include sensitive customer information in support requests unless your organization policy allows it.
  • Current report calculations run in the browser frontend. The resolver stores configuration and settings. The current codebase does not include an external backend reporting warehouse.
  • Local mock mode uses browser localStorage for local development and screenshot generation.

Troubleshooting

If users report different results, compare their Jira issue access, project permissions, filter permissions, and selected report settings.