Reference
Glossary
| Term | Definition |
|---|---|
| Pulse Score | A health score from 0 to 100 summarising the condition of a section, item, or overall Jira environment. |
| Grade | A letter rating (A–F) based on the Pulse Score. |
| Finding | A detected issue, risk, or cleanup opportunity. |
| Clean Signal | A passed check showing that Pulse AI did not detect a specific risk. |
| Orphaned | Object has no active usage or reference - no projects assigned, no schemes referencing it, or no workflow usage. |
| Unused | Object has zero usage - unused priorities, resolutions, fields, or config objects with no assigned usage. |
| Stale | Object or issue has not been used or updated recently. Common thresholds: 90+ days for backlog/projects/fields/filters; 14+ days for stalled in-progress issues. |
| Stale Backlog | For projects: stale issues ÷ total issues > 30%. |
| Dormant | User: active account with last activity older than 90 days. |
| Inactive | User: active === false. Project: activity older than threshold or all issues inactive. |
| Bloated | Screen: available field count exceeds 50. |
| Duplicate | Same name or same signature exists more than once. |
| Widely Shared | Object used across many projects or schemes beyond a threshold, increasing blast radius if changed. |
| Missing Default | Scheme has no default issue type, security level, or workflow depending on section. |
| No Category | Status has no valid category assigned. |
| No Security Levels | Issue security scheme has zero levels defined. |
| Publicly Shared | Filter share permissions include public or global access. |
| Risky Deletion | Custom field is stale or unused but still appears on screens - cleanup may break users. |
| Guard | Protected or system-managed object; should not be treated as a normal cleanup target (e.g., Default Permission Scheme, system groups). |