FAQ & Troubleshooting

Click Refresh. The first scan takes 10–30 seconds depending on project size.

If the dashboard is still empty after refreshing:

• Make sure your project has at least some issues.
• Check Excluded Issue Types in Settings — some types may be excluded.
• If using a Custom JQL Filter, verify it doesn’t narrow scope too much.

Congratulations — your project is healthy! This message appears when no issues exceed any detection thresholds. It means:

• No items are stagnating longer than expected
• Workload is balanced
• No approaching deadlines at risk
• Backlog is relatively fresh

Your Health Score should show Grade A or Grade B in this case.

Yes, fully! Delivery Doctor automatically follows your Jira theme settings. If you have Dark Mode enabled in Jira, the app will render in dark mode as well.

Thresholds are based on industry best practices and research, not arbitrary numbers:

Making thresholds configurable often leads to teams setting lenient values that mask real problems. The adaptive baseline (p85) already customizes stagnation thresholds to your team’s actual pace.

Auto-sync runs every 30 minutes by default. Auto-sync runs silently in the background — no countdown or indicator is shown. You can also:

• Click the Refresh button for an immediate manual refresh.
• Adjust the sync interval in Settings: 30 min, 1 hour, 2 hours, 4 hours, 8 hours, or 24 hours.

No. Delivery Doctor is a Forge app built exclusively for Jira Cloud. It does not support Jira Data Center or Jira Server.

Delivery Doctor tracks when an issue entered its current status, not the generic "Updated" timestamp. Comments, label changes, or field edits don't count as meaningful progress.

Example: An issue has been in "In Progress" for 14 days, but its "Updated" field says "2 days ago" because someone added a comment. Delivery Doctor correctly reports 14 days of stagnation.

An unassigned task is an In Progress issue with no assignee. These are always flagged as Critical because work without an owner is unlikely to progress reliably.

This is Highlander Deduplication in action — each issue appears as one row per section, with the highest-priority badge shown.

• Hover over the issue to see all detected patterns.
• A colored border on the row indicates 2 or more patterns are active.
• Snoozing the issue dismisses all its patterns at once.

Learn more about Highlander Deduplication →

Use the Pattern Filter in the TopBar. Click the filter icon (next to Refresh and Settings) to open a dropdown with checkboxes for each pattern. Uncheck patterns you want to hide.

• A badge (e.g. "5/8") on the icon shows how many patterns are currently active.
• At least one pattern must remain enabled at all times.

For permanent changes, use the Settings page instead.

Learn more about Pattern Filter →

Estimation Variance requires three things to be in place:

• Time tracking must be enabled in your Jira project.
• Issues must have original time estimates set.
• Team members must have logged time against those issues.

If none of these conditions are met, the pattern shows as "Unavailable" on the dashboard.

Follow this checklist:

1. Make sure you’re inside a Jira project, not the Jira home screen.
2. Look for it in the project tab bar at the top of the page, not the left sidebar.
3. Verify the app is installed at your site (Site Settings → Apps).
4. Hard-refresh the page (Cmd/Ctrl + Shift + R).

This means the project has no issues yet, or it uses a workflow without standard statuses. Create at least one issue in the project, then refresh the setup wizard page.

Large projects (1,000+ issues) take longer on the first scan. The app uses smart data fetching to optimize subsequent scans. If it takes more than 2 minutes, check your browser console (Developer Tools → Console) for errors.

This is usually a temporary Jira API issue. Try the following steps:

1. Wait a moment and click Refresh.
2. Check status.atlassian.com for any ongoing incidents.
3. Try logging out of Jira and logging back in.
4. Clear your browser cache and reload the page.

Check your settings:

1. Excluded Issue Types — Check if you’ve excluded types you expect to see.
2. Custom JQL Filter — Verify it’s not narrowing scope too much.
3. Blocker Detection (Flag or Status) — Make sure the correct method is selected.

After adjusting settings, click Refresh to re-analyze.

The Health Score formula is:

Score = 100 - (10 x CRITICAL) - (3 x WARNING)

To verify:

• Check each section and count the number of Critical and Warning patterns.
• Snoozed patterns do not count toward the score.
• Verify the issue counts match what you expect based on your filters.

Large projects (1,000+ issues) naturally require more time to analyze. Initial loads can still take 10–30 seconds.

To improve performance:

• Use issue type filters to narrow down the scan scope.
• Check your browser's developer console (F12) for errors.
• Try a different browser to rule out extension conflicts.

The wizard appears when setup hasn’t been completed successfully. Make sure to finish all steps and click “Go to Dashboard” on the final screen. If it persists:

1. Try completing the wizard again — click “Start data collection” and wait for sync to finish.
2. If errors occur during sync, check your browser console (Developer Tools → Console).
3. If the issue continues, contact support.

After closing the issue modal, Spot Refresh re-fetches only that single issue. Pattern counts and the Health Score may be slightly out of sync until the next full Refresh runs.

When you Cmd/Ctrl+Click an issue, it opens in a new browser tab. The dashboard tab has no way of knowing when you make changes in the other tab. Click Refresh after returning to the dashboard to pick up any changes.

The Refresh button is disabled for 60 seconds after each press. This protects the Jira API from hitting rate limits. Spot Refresh from issue modals still works normally during the cooldown.

Each scan covers up to 5,500 issues across four streams: 1,000 In Progress + 2,000 To Do + 500 Graveyard + 2,000 History. On very large projects, some issues may fall outside the scan window. See Pincer Strategy for details.

Delivery Doctor only fetches the changelog for In Progress issues. This speeds up loading by ~80%, but it means Rework and Aging Impediments patterns only work for active tasks.

Delivery Doctor accesses the following data from your Jira instance:

• Issue data — summary, status, assignee, dates, story points, and changelog.
• User data — display names (for assignee information).
• Project data — workflow statuses and issue types.

All data stays within Atlassian infrastructure. No data is sent to external servers.

All app data is stored in Forge Storage — Atlassian's secure key-value storage system. Data is encrypted at rest and scoped to your Jira site.

Yes. Pattern data is visible to all project members. Snoozed patterns and app settings are shared across the entire project — they are not per-user.