Jira Cloud · Forge · version 3.8.0
TeamGuard for Jira
A read-only project view for delivery dates, overdue work and assignment distribution, with optional inactive configuration drafts.
How it works
- Open TeamGuard from Jira and choose a project. No project is preselected; the app does not request issue data until you choose one.
- Review the overview, delivery-risk list and team assignment counts. Signals use Jira fields visible to your account. Missing due dates are shown as “No signal”, not as overdue.
- Use configuration tools to validate and save an inactive draft. Drafts do not activate rules, change Jira issues or send notifications.
- Administrators can review draft history, restore a prior draft as a new inactive draft, or delete a draft after explicit confirmation.
Data and permissions
TeamGuard requests Jira work read access and app storage. It reads issue key, project key, summary, status, due date, labels, priority and assignee display name/account ID for the current view, subject to the signed-in user’s Jira access. These issue fields are processed in memory and are not stored by TeamGuard. The app does not request issue descriptions, comments or attachments.
Forge storage is used for configuration drafts: a random draft ID, creation and expiry timestamps, project keys, inactive rule proposals and an optional reference to a prior draft. No author ID or Atlassian account ID is stored with a draft. Drafts expire within 365 days; an administrator can delete a draft from active app storage.
What TeamGuard does not do
- It does not write to Jira issues.
- It does not activate automation rules or send alerts.
- It does not calculate team capacity or individual performance. Assignment counts are descriptive only.
Limitations
Signals depend on Jira fields and permissions, and can be incomplete or out of date. Review the underlying Jira issue before acting. TeamGuard should not be the sole basis for employment, performance, safety or other consequential decisions.