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; } } }

How to solve - Field with the same name already exists for this project?

Mart Postma

Currently I'm trying to setup my new JPD environment. When trying to create a new field for my list view, I get the following error message:

As the JPD project is a new project and has no other custom fields yet, I can't find the underlying issue of this error message.

How can I solve this?

Accepted answers

Rohan Swami

Hi @Mart Postma "Priority" is a special system field all throughout Jira products and the name can't be used as a custom field in any Jira project, including Jira Product Discovery. You can use similar words such as Importance or prefixes/suffixes like Priority Rank.

All comments

Rohan Swami

Mart Postma

Okay clear, thank you - will use the work around then. The ambiguity of the error message is however a bit confusing to me, because it refers to "this" project = this JPD project, hence leading to the confusion here. Thank you!

Ted_awmefe

Hi @Rohan Swami - I have some similar feedback - the Priority field is simply missing from the fields available within JPD. I would expect it to be available as a system field similar to other fields within JPD.

Do you know why Priority is not available?

So when the user sees Priority missing from the dropdown, they try to create it and then the user gets the error message as stated above which states that Priority is already a field in "this project".

This is confusing as it turns out the priority field is actually not available in ANY project in JPD.

So changing the error message to something like "Priority is not an available field in JPD" or something would make more sense (or enable priority as a field in JPD to avoid confusion)

I will follow your advice though and create a field called "Priority Rank". This just seems like unnecessary work as I would expect Priority to be available "out of the box" for JPD without having to create this workaround

Welcome!

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