We propose adding a "Scheme for Plans" feature to Plans, similar to how Jira currently uses schemes for projects (e.g., permission schemes, notification schemes, field configurations). This feature would allow administrators to define and manage reusable configurations for Plans, enabling consistency, efficiency, and easier management across multiple Plans.

 

Additional information:

Problem Statement:
Currently, when creating a new Plan in Plans, administrators and project managers must manually configure layout, field visibility, views, filters, and other settings.
This process is time-consuming and error-prone - particularly for organizations managing multiple teams or departments that follow the same planning structures.
Without a way to reuse configurations, teams often face inconsistent experiences across Plans and spend unnecessary time replicating settings.

Furthermore, when an organization wants to update a specific configuration globally (for example, introducing a new field, changing a layout standard, or adjusting default filters), there is no centralized way to apply those changes across all Plans. Each Plan must be updated individually, which increases administrative overhead and the risk of inconsistency.
Introducing configurable Plan Schemes would allow such organization-wide changes to be made once at the schema level and automatically reflected in all associated Plans.

Proposed Solution:
Introduce a "Plan Scheme" concept that allows reusable configuration templates to be defined once and applied to multiple Plans.

Key Configuration Areas:
1. Layout & Appearance
Column layout
Grouping and hierarchy display
Color schemes or custom visual settings
2. Fields
Which fields are visible or hidden
Field order and labeling
Field editability options
3. Views
Available views (e.g., timeline, list, team, capacity)
Default view settings
Saved custom views shared via the scheme
4. Filters & Criteria
Saved filters and query definitions
Default issue sources (boards, projects, filters)
5. Other Plan-Specific Settings
Scheduling rules
Capacity and velocity settings
Dependency and roll-up configurations

How It Would Work:
Administrators create a new Plan Scheme and define configurations.
Schemes can be assigned to new or existing Plans.
Changes to a scheme can optionally propagate to all Plans using that scheme (similar to project schemes).

Benefits:
Consistency: Ensures standardized configurations across all Plans in an organization.
Efficiency: Reduces setup time and effort when creating or maintaining multiple Plans.
Scalability: Makes it easier to onboard new teams or projects with predefined planning standards.
Governance: Improves control over how Plans are structured and displayed across the organization.

Example Use Case:
A large enterprise manages 20+ product teams, each using their own Plans. All teams should follow the same layout. Currently, an administrator must manually recreate these settings in every Plan.
With Plan Schemes, the admin could define the configuration once, apply it to all Plans, and ensure consistent updates organization-wide.

Potential Future Extensions:
Scheme versioning and audit history
Scheme inheritance (e.g., team-specific overrides)
Import/export capabilities for sharing across Jira instances