FAQ

Common questions about StatusPath Reports.

Why can’t I find some work items?

Check the Work item scope first. The selected Project, Saved filter, JQL, Sprint, or Epic must include the work item before it can appear in the report.

Then check the Work item date range. A work item can exist in Jira but still be excluded if the selected date field and range do not match it.

Finally, check Jira permissions. StatusPath Reports can only report on data that Jira makes available to the current user and app context.

Why are results different from another app?

Different apps may use different calculation windows, calendars, timezone rules, status mapping, or changelog handling.

When comparing results, align these settings first:

• Report type.
• Work item scope.
• Work item date range.
• Trim History.
• Work schedule and business hours.
• Timezone.
• Duration format.
• Included statuses, groups, and filters.

If the settings are not identical, differences are expected.

Why is Time in Status empty?

Time in Status needs status history for the selected work items. It may be empty when the selected work items have no usable status history, when Trim History removes the relevant period, or when the current user cannot access enough changelog data.

For Issue Activity, the current work item itself must have status history available.

Why is Time in Assignee empty?

Time in Assignee needs assignee history. It may be empty when work items never changed assignee, stayed unassigned in a way that does not create usable history, or when Trim History removes the relevant period.

Use a narrow work item scope and Table view to confirm whether assignee duration rows exist.

Why does a status column not appear?

Status duration columns are based on the report data and the current column configuration. A status may not appear when:

• No selected work item has usable history for that status.
• The status is not selected in Columns Manager.
• The current report type does not use status duration columns.
• Trim History removes the status segment from the calculation window.

Open Columns Manager if you need to check selected statuses or status groups.

How do Jira permissions affect reports?

Jira permissions affect which projects, filters, work items, fields, and histories the current user can access. StatusPath Reports should be read as a reporting layer over Jira access, not a replacement permission system.

A saved report or dashboard gadget can store a setup, but the result still depends on the Jira access of the user and context running it.

What is the difference between Work item date range and Trim History?

Work item date range selects which work items enter the report. For example, it can include work items created, updated, or resolved during a selected period.

Trim History changes the history window used to calculate those selected work items. It does not select the work items by itself.

If a work item is outside the Work item date range, Trim History will not bring it back into the report.

How do business hours affect results?

Business-hour calculations use the selected Work schedule. Only time that overlaps the selected calendar’s working days, working intervals, timezone, and exceptions is counted.

Changing the Work schedule can change Time in Status, Average Time in Status, Time in Assignee, charts for duration reports, and exported duration values.

Does export match the table?

Table export uses the current report configuration, column state, supported filters, sorting, duration Format, and Calendar.

Export can load the full current report result before generating the file, so it should not be read as only the rows currently visible in the viewport. Export size and performance can still depend on browser memory, Jira data volume, report type, and API/runtime behavior.

Chart export is separate from table export. See Export and Chart view.

What does a saved report save?

A saved report stores reusable report setup, such as report type, work item scope, date filters, Trim History, duration Format, Calendar id, view mode, fields, status or assignee columns, groups, sorting, supported filters, duration filters, and chart settings where supported.

It does not store frozen Jira result rows, changelog copies, generated export files, or an open modal/menu state.

See Saved reports.

Who can see my saved reports?

Saved reports are stored by the app. The current implementation stores an owner account id when a preset is created, but complete owner-based isolation is not enforced across all saved-report resolver actions.

Do not rely on saved reports as a privacy boundary until your Jira site has verified the behavior you need. Jira permissions still apply when the report is run.

Why is a chart empty?

A chart may be empty when:

• The report has no rows.
• The selected chart does not apply to the report type.
• The selected report type or data does not support the chart view.
• Current filters remove the values needed for the chart.
• A duration chart has no duration values in the selected history window.

Switch to Table view to confirm whether the underlying report has rows.

Why does JQL validation fail?

JQL validation uses Jira’s validation behavior. A query may fail because the syntax is invalid, a field or value is not available, the user lacks permission for part of the query, or Jira rejects the expression.

Correct the JQL before running the main report or saving Dashboard Gadget setup.

Why is Issue Activity empty?

Issue Activity analyzes only the current Jira work item. It may be empty when:

• The current work item has no status history for Time in Status or Status Count.
• The current work item has no assignee history for Time in Assignee.
• The current work item has no status transitions for Transition Count.
• The current user cannot access the work item or its changelog data.
• The work item changed recently and the module needs to be refreshed.

Use the main report page if you need to compare the work item with a larger scope.

How do I contact support?

Contact BlueGrove Labs at support@bluegrovelabs.com, or use the BlueGrove Labs support portal.

See Support for what to include in a support request.