Jira Dashboard Naming Policy Template

We have prepared a Policy Template that you can use to standardize dashboard naming across your organization. It is designed in a clear, actionable format that you can easily download or adapt for documentation, Confluence, or even onboarding guides.

Document Title	Jira Dashboard Naming Policy
Version	1.0
Effective Date	Insert Date
Owner	Jira Admin Team

1. Purpose

This policy defines a standardized naming convention for Jira dashboards to improve discoverability, consistency, and maintainability in our Jira environment.

2. Scope

This policy applies to all users who create or manage dashboards in Jira, including personal, team, departmental, and global dashboards.

3. Naming Convention Format

General Format:

Project Key/Business Unit: Purpose - Sub-purpose (Timeframe/Status)

Component	Description
Project Key/Business Unit:	By starting with the project key, it introduces hierarchical organization and ownership implicitly The alphabetic ordering will allows related dashboards to be grouped together This also helps users to quickly filter relevant dashboards Sometimes a dashboard may be relevant to multiple Jira projects, you can differentiate them by enclosing the Business Unit (e.g. Department) code in square brackets []
Purpose	A short summary on purpose of the dashboard
- Sub-purpose	An optional addition prefixed with a dash if multiple dashboards are required for 1 purpose Typically this is not required 1 possible example is a dashboard with many gadgets split into mutiple dashboards for faster loading
(Timeframe/Status)	The chronological information enclosed in brackets () help users to identify its relevance at a glance It could be time periods, sprint numbers, or version numbers or even phases Some possible values may be Monthly 2025 Q4 Current Draft Deprecated Testing

The naming structure encompasses the following principles:

Maintain a consistent naming format to avoid unnecessary confusion
Use descriptive names to indicate what the dashboard is about
Use full words instead of abbreviations unless they are widely recognized
Include relevant keywords that people might search for
Include temporal indictors to help users distinguish between current and historical dashboards

4. Abbreviation Standards

Use team and department abbreviations consistently. Example list:

Department	Abbreviation
Information Technology	IT
Human Resources	HR
Finance	FIN
Sales	SALES
Marketing	MKT

5. Additional Rules

Use Title Case for each segment
Avoid generic names like “Dashboard 1” or “My Dashboard”
We recommend to share only to the relevant users by using project roles
Do not share the dashboards with “Anyone”
Do not include sensitive information in dashboard names
Review and update dashboard names if their purpose or ownership changes

6. Dashboard Ownership and Review

Every shared dashboard must have a clear owner (the creator or designated team lead).
The Jira Admin team will conduct biannual audits to identify:
- Orphaned dashboards (owner left or inactive)
- Dashboards not viewed in 6+ months
- Duplicate or obsolete dashboards

7. Consequences of Non-Compliance

Dashboards that do not follow the naming policy may be:

Renamed by the Jira Admin team
Removed from shared visibility
Flagged during system audits

8. Review Cycle

This policy will be reviewed every 12 months or after major changes to Jira dashboard capabilities or governance requirements.

📩 Contact for Questions:
Email: jira-admin@[yourdomain].com
Slack: #jira-support