JPD and customfields

[Olivier GIRAULT]

Hello everyone :-)

We are studying the possibility of installing JPD on our production instance in order to link jpd and our backlogs under JIRA.

However, with each new JPD project, it creates new fields, which are all available as many times as there are projects in the list of available fields for e.g. gadgets ... search ticket views...

How do you work with this constraint in projects combining JPD and jira?

Thank you for your feedback :-)

Olivier

[Hermance NDounga · Accepted solution]

Hello Olivier, 

We received this feedback from our customers and we are currently addressing it. You can find it mentionned under the item Use a project as a template to create other projects 

of our public roadmap. 

We will ship this enhancement in the upcoming months: only one of each field will be created, regardless the number of projects you'll have. You won't need to migrate anything. 

Stay tuned in community or our roadmap to be aware of the release of thefeature. 

Cheers, 

Best Regards,
Hermance
Product Manager @ Jira Product Discovery

[Bill Sheboy]

Hi @Hermance NDounga 

The roadmap link you provided appears to be the internal one for Atlassian team members.  Did you instead want to provide this one for the public view of the roadmap:

https://atlassian-product-managers.atlassian.net/jira/discovery/share/views/a0af4caf-5f1b-42be-8c57-24d1080122bc

From this article:

https://community.atlassian.com/t5/Jira-Product-Discovery-articles/What-are-we-up-to-Public-roadmap-for-Jira-Product-Discovery/ba-p/2880405

Kind regards,
Bill

[Hermance NDounga]

Yes thank you, I changed the link in my comment. 

[Bill Sheboy]

Hi @Olivier GIRAULT 

From my perspective, JPD is based upon team-managed projects (TMP), and thus you are correct: many of the project-specific, custom fields are unique for each project.

There are several ways to mitigate those differences:

• The simplest is to only use one JPD project.  If the JPD project is your "portfolio" perhaps only one is needed to feed into the software projects for "delivery".  When that is not possible...
• Some of the global fields (i.e., company-managed project fields) can be added to JPD and TMP projects for reuse.  Only some of the field types are supported this way; please read here to learn more: https://support.atlassian.com/jira-product-discovery/docs/create-and-manage-global-fields/
• Automation rules can help synch / update data between JPD and other projects.  The key is ensuring the rule scope covers the projects needed and the correct custom field ID values (rather than the field names) are used for each project.  Additionally, the fields may need to be edited with JSON expressions rather than using the automation edit actions.

Kind regards,
Bill

[Olivier GIRAULT]

Hello to both of you, thank you for your comprehensive and detailed feedback.

It gives us confidence in our ability to offer this solution to new users without impacting existing ones.

And yes Bill, I think we'll definitely use global fields, but a single project will be too complicated because we have so many different entities.

I keep the idea of automation between projects in the back of my mind.

Best Regards,

Olivier