Jira Product Discovery is all about empowering teams to stay laser-focused on delivering customer value. Each Jira Product Discovery project can be used independently by any team to create their own views and any project fields they need to help describe, organize, and prioritize their ideas and focus on the right outcomes.
But when teams are siloed in their own projects, they end up creating different frameworks and terminology – ultimately speaking different languages. This makes it harder for product leadership to get a common vision across products and adds extra workload to admins tasked with maintaining shared concepts across projects.
To drive consistency and alignment across teams and reduce administrative overhead, we’re excited to introduce Global Fields in Jira Product Discovery.
Achieve consistency across projects
Say goodbye to miscommunication and crossed wires, and hello to cross-team alignment. With Global Fields, create a field that can be used across multiple projects, or even include existing Jira fields in your Jira Product Discovery projects.
For example, ensure all teams use the same Roadmap field with the values “Now,” “Next,” and “Later,” or create a global RICE score, relying on the fields Reach, Impact, Confidence, and Effort. Now, every team, no matter what feature or product they are working on, can use the same language, definitions, and criteria to describe and evaluate their ideas.
Preserve your teams’ autonomy
Product managers’ days are filled with disruptions, but when it comes to building their roadmap, they can hit the ground running by using existing global fields, ensuring they align with organizational standards from the start. Standardization doesn’t have to come at the cost of flexibility either. Product teams can still have the freedom to create project-specific fields as needed, without disrupting the overall structure.
With global fields and project fields, you can now preserve each team’s autonomy while keeping them connected with the same language and terminology. This allows for organizations to be principle-driven and not process-driven.
No more admin overhead
As an admin, keeping peace and order takes more time and energy than you have in a day. Good news – recreating the same fields over and over in each new project and maintaining them is, well, over.
You can now save time and reuse global fields when you first create a project for simplified setup, and when it comes to making changes to a global field, do it once and it will be reflected across all projects. We’ve also made it easy for admins to adopt global fields with the ability to copy project fields into global fields with just a few clicks.
When should you use global fields?
- You want to standardize terminology (e.g. consistent field names and values) across different projects.
- You want to reduce admin overhead by creating and updating fields one time in one place, and have those updates visible across all projects.
- You are using two discovery projects and often move ideas from one project to another, needing global fields and values to be retained when moving.
- You want to leverage Jira Product Discovery Roadmaps in our Premium plan (available in early access) to see a roll up of multiple projects within one view.
What’s next ?
Learn how to get started with Global fields. Global fields are just the beginning of our journey to help product organizations scale their product practice across teams. We’re working on reducing the admin burden and improving consistency across Jira Product Discovery projects so stay tuned!
To see full demos of global fields or leave questions and feedback, visit our post in the Atlassian Community!