Components as project phases

[Toni Goode]

We are refining the JIRA topology for a large multi-program portfolio and would like confirmation on recommended practices for using Components and Labels.

Our structure includes several programs, each containing multiple individual projects, all with the same lifecycle phases (Requirements, Design, Development, QA, UAT, Prod Readiness, Prod Support, Risk, Decision).

We are considering the following approach:

• Use Labels to identify Program and Project.
• Use Components to identify the structured phases of work that apply consistently across all projects (Requirements, Design, Development, QA, UAT, etc.).

Our question is:
Is it aligned with Atlassian best practices to use Components for governing project phases, while using Labels to identify individual projects and programs?

We want to ensure we are using Components and Labels in the way JIRA was intended, particularly for accurate filtering, consistent reporting, and scalable dashboards across many projects.

[Trudy Claspill]

Hello @Toni Goode 

Welcome to the Atlassian community.

Which Atlassian products do you have available to you? Are you using only the Jira product? Do you have Jira Service Management?

What type of subscription do you have; Free, Standard, Premium, or Enterprise?

Is this a new Jira environment that does not already contain data? Or are you trying to add this multi-program portfolio into an existing Jira instance?

Do you have any third party apps in this environment to augment native functionality?

Are you open to:

1. upgrading your product subscription
2. acquiring additional Atlassian products
3. acquiring third party apps
4. Working with an Atlassian Solution Partner to plan for the best implementation to meet your requirements? (Disclosure: I work for Praecipio, an Atlassian Platinum Solution partner.)

The best practice recommendations will depend on the products and subscriptions available to you.