8. Troubleshooting and FAQ

If you're facing an issue, we've compiled answers to some frequently asked questions to assist you.

A: This typically indicates one of two scenarios:

1. The issue did not spend any time in that status, as it was transitioned through immediately.

2. The issue completely bypassed that status within the workflow.

A: This issue is typically linked to the distinction between Calendar Time vs. Business Time setting.

• Too high: Your app is probably using Calendar Time, which measures time continuously, including nights and weekends.

• Too low: Your app is likely using Business Time, which only considers the working hours specified in your Work Calendar.
  Please reach out to your administrator to confirm which setting is currently in use.

A: Check your filters!

1. JQL is too restrictive: Your JQL query may be too narrow. Test it in Jira's native issue search first.

2. Incorrect Filter Selected: Make sure you have the appropriate Project, Assignee, or saved Filter selected.

3. Date Range: If your JQL uses a date range, ensure it's correct.

4. Jira Index Exception: Please contact the administrator to rebuild the index and try again.

A: Large reports can indeed take time to load. Here are some suggestions to enhance performance:

1. Narrow your query: Consider using a more specific JQL query or a smaller date range. This will help reduce the volume of data being processed.

2. Contact your admin: Reach out to your administrator, as they can modify the "Maximum Issues Per Query" setting. Lowering this limit may improve performance, especially in very large Jira instances.

A: Your Jira administrator has configured access permissions for this app. You need to be part of a user group that has been granted access to that specific module (e.g., Reports, Work Calendars). Please contact your Jira administrator and request the necessary permissions to be granted.