📣 Feature update: JPD system fields are turning global

[#1]

UPDATE: June 18, 2025

All Jira Product Discovery projects will now exclusively use global system fields. If you have been using system field keys in your automation or JQL, you may need to update them to ensure they continue functioning correctly as explained here. 

We apologize for any inconvenience this may have caused and are available to assist you with any issues.

---

Summary

We’re making changes to JPD system fields to make them global. This will solve many issues in sites with many JPD projects.

⚠️ Note to customers with automation rules, Jira filters and workflow rules using the fields used to “archive” ideas today: some of them break in specific scenarios. Read this to learn more about this and how to mitigate these issues.

Why we’re making this change

As organizations expand the use of Jira Product Discovery to more teams, Jira admins gave us the feedback that we need to make it easier for them to manage JPD fields in Jira.

JPD projects currently support 3 types of fields:

• Project fields: custom fields created and managed in each project.

• Global fields: custom fields created and managed at the site level, then added to projects. Any change to the configuration of global fields is automatically reflected across all projects

• System fields: these are fields that are there by default in every JPD project and you can’t edit them - for example the “reporter”, “creator”, “delivery progress”, “comments” or “insights” fields - see the full list here.

Before, every time you created a new JPD project, the system created a copy of most of the JPD system fields: if you created 100 projects you’d get 100 instances for each of these fields. For example, in the picture below, you see 5 copies of the Delivery Progress field, one for each of the 5 JPD projects in this site.

As a result, Jira admins struggled to keep their instances clean. This had an impact on the end user experience as well: when filtering ideas in Jira Filters or Confluence macros users got confused about how to write their JQL queries.

Once we are done with this change, you will only get one copy of the Delivery Progress field in Jira.

This change will be carried out in stages:

• Stage 1: any JPD project created after Mar 14, 2025 have system fields that are global

• Stage 2: all other existing JPD projects' system fields will be made global. This change is currently scheduled for May 31, 2025.

Until we complete Stage 2, your Atlassian site will have a mix of global JPD system fields and project-level system fields, as depicted below.

What does this mean for you?

For new JPD projects you created from Mar 14, 2025 : no impact.

For projects created before that date:

1. None of your data will be lost

2. Some automations, Jira Filters, or workflows that read or edit fields used for archiving ideas might break while we are working on Stage 2, please read this community post to mitigate the possible issues.

Thank you for your understanding as we work to make JPD easy to manage at scale. In the meantime, please drop feedback or questions in this community post or reach out to support if you face any issue.

Cheers,

Amina