Jira Admin Configuration Guide

Following are the tabs for Jira admin

1. Board Management Tab

This tab serves as the central directory for every standup ritual created across your Jira instance.

Key Capabilities:

• Search & Audit: Use the search bar to find specific board configurations by name or Jira board ID.

• Facilitator Management: Admins can see the current facilitators for any board and add/remove members from the list directly, even if they aren't part of the team.

• Governance Kill-Switch (Enable/Disable):

  • Toggle Off: Disabling a board immediately blocks all new standup submissions. The existing data remains visible in "Read-Only" mode.

  • Override: If a facilitator pauses a standup, the Admin can override and re-enable it from this screen.

• Metadata Visibility: View when a standup configuration was first created and its current status (Active vs. Admin Disabled).

Open

2. Global Settings Tab

Configure the app-wide behavior and data residency rules.

Data Retention Period

To comply with GDPR, CCPA, or internal storage policies, you can set a global expiration for standup data:

• Available Options: 30, 60, or 90 days (default is 90).

• Automated Cleanup: The application runs a daily background job to permanently delete records older than this period.

• Covered Data: This affects all standup submissions, mood responses, and historical blocker records.

Open

3. Reset App Tab (Danger Zone)

This section is for high-consequence administrative actions that cannot be undone.

Reset All App Data

This tool is used for a "factory reset" of the application. It is primarily used when transitioning from a trial to a production environment or when performing an instance-wide cleanup.

• What is deleted?: All board configurations, all facilitator lists, all standup submissions, and all resolution notes.

• What is NOT affected?: This action NEVER touches your native Jira issues, comments, or attachments.

• Safety Protocol: To prevent accidental deletion, you must type "DELETE" in the confirmation box to initiate the asynchronous background reset.

• Background Jobs: Large deletions are processed in the background. You can monitor the "Processed Count" in the status modal while the reset is in progress.

Open

4. Admin vs. Facilitator Scope