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

[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