nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

issue with duplicated fields with other non-product discovery projects

Sabine Lambrecht

Hi,

When working with Product Discovery in Jira, we find it convenient to create new fields. However, this has resulted in duplicated fields with our other Jira products. Consequently, we are facing challenges when utilizing the Advanced Issue Search feature in Jira and Structure. Is there a way to prevent the use of identical field names that already exist in other projects or other alternatives to resolve the issue? We would greatly appreciate any guidance or suggestions to address this issue effectively.

Accepted answers

All comments

Kyren Cabellon

Hi @Sabine Lambrecht

I have encountered the same problem with other Jira Projects as I created new custom fields.

I have discovered the Global Custom fields which should be found here /secure/admin/ViewCustomFields.jspa

I would create the new fields instead of it in the specific project so we can reuse it and not have duplicate fields.

Omer Meshar_0f60qw

@Kyren Cabellon Can you see custom fields of JPD in this view? I can't find them there..

Hermance NDounga

Hello Sabine,

As Jira Product Discovery projects are team-managed projects, any fields you create in them are self-contained, and we don't prevent you to reuse the name of another field that exists in another project.

We are aware that team-managed fields do not surface well in the global Jira functionalities (advanced search, filters, dashboards...) . For the moment, the only way for you to manage these duplicates, when you spot one, is to change the name of the Jira Product Discovery field in one of your projects.

Just for me to better understand your usecase, do you have fields with duplicated names because

you have created custom fields in other Jira projects that suit your usecase - for example you created a "Roadmap" field in Jira Software, and you got now new roadmap fields because of Jira Product Discovery

You are "forced" to create duplicated fields in Jira Product Discovery named "Release" or "components" because you cannot reuse the ones provided by other Jira products?

(or both 😅)

We are currently exploring this problem space so I'd really to hear more about your use case.

Cheers

Hermance

CC_pcyuge

I have created a hand full of duplicate custom fields in JPD because they already exist on the software side. I add a suffix to the JPD field so I can easily determine the matching software field. For example, "Program Increment" on the software side equals "Program Incrementor" on the JPD side. I am putting in place automations to keep the fields in sync.

Additional fields that will be synced: actual start date, actual end date, assignee, and Program Increment.

Sabine Lambrecht

Hello Hermance

It's actually both.

Reasons to use the already existing fields in our other Jira products

- these fields serve a specific purpose that our team is already familiar with, ensuring consistency across projects. Moreover, if these fields are drop downs the values associated with these fields are already defined, making it easier for us to select appropriate options.

- having the ability to reuse fields in JPD is important for reporting and data analysis purposes. By using consistent field names and values, we can generate accurate and meaningful reports that provide insights across different projects. This enhances our ability to track progress, identify trends, and make informed decisions.

- avoiding duplicated fields is crucial for maintaining data integrity and preventing confusion. When fields have the same name but serve different purposes or have different value sets, it can lead to errors and inconsistencies in data entry. By reusing existing fields, we reduce the likelihood of duplicate or redundant fields, ensuring cleaner and more reliable data.

- by utilizing the existing fields, we can consolidate and streamline our processes. This allows us to effectively manage our backlog of ideas by moving existing tickets to JPD while preserving all relevant information associated with these tickets.

If you have any further questions or require additional information, please feel free to contact me. I appreciate your efforts in exploring this problem space and look forward to any enhancements that may address these concerns.

Sabine

Kyren Cabellon

@Omer Meshar Apologies, upon double checking I have found out that this does not work with Jira Product Discovery. I assumed it would work since it worked for my Jira projects.

Hermance NDounga

Hi Kyren,

I just wanted to let you know that we are opening an EAP for Global fields -> You can sign up here : Early access program: Global fields

Cheers!

Hermance NDounga

Hi Sabine,

We are opening an EAP for Global fields -> You can sign up here : Early access program: Global fields

Cheers,

Hermance

Welcome!

It looks like you're new here. Sign in or register to get started.