Jira Product Discovery Artifacts

[Mathew Lederman]

Do JPD artifacts impact the global environment like a company-managed project? Or is it fully similar to a Team-Managed project in that the artifacts created are specific and exclusive to each project? 

As we work to open JPD to our users, I want to make sure we instill best practices and don't create a ton of artifacts (custom fields, statuses, etc.) for us to clean up later.

[Bill Sheboy]

Hi @Mathew Lederman 

In my opinion, it is somewhere in the middle of what you ask...

Jira Product Discovery (JPD) appears to be based upon team-managed projects (TMP), and so the fields, configuration, licensing, etc. are independent of other company-managed projects. 

However, some of the limitations in JPD (as with TMP) may require using global / company managed fields to solve problems.  And thus a global field could be added for JPD-only use and the admins will need to monitor they do not associate it with other projects unintentionally.

Regarding workflow, I would expect ideation and other similar portfolio practices to have different status values.  Understanding how / when they map to the other projects' workflows may be relevant when using the linked "Delivery Tickets" features to assess / communicate roll-up of progress of Ideas.

Automation rules are another wrinkle:

• they have separate and additional execution limits,
• sometimes require "site" global (or multiple-project) scope even though within JPD automation they appear to be mixed project / global; what the rule does is the key to knowing the correct scoping due to a "Creator" user's permissions being different from the existing "Automation for Jira" super-user-like permissions.

Kind regards,
Bill

[Mathew Lederman]

@Bill Sheboy appreciate the quick response, as always.

My concern is that giving regular users Admin privileges in the JPD project also gives them the ability to create fields, workflow statuses, etc. I want to make sure they're not creating global artifacts like custom fields that get used once and don't abide by our enterprise standards.

If they do create such artifacts, our only recourse as Jira admins would be to restrict project admin access, which goes directly against the purpose of creating a JPD project.

From my testing it seems that project admins are only able to create items within the scope of their project, and while they are able to utilize global fields, only a Jira admin can create/scope those fields appropriately.

Thanks,

Mathew

[Bill Sheboy]

Yup, "great power, great responsibility..." leading to "oops...umm, can someone fix that for me..." for all things TMP-like :^)

At my last company, we used training, documentation, and delegation to help a bit:

• only two of the Creators were also admins for the JPD project
• the site admins partnered to inform / train those specific people on better practices
• we allowed them to manage requests from the other Creators for new fields, etc.
• we had regular touchbase chats to learn what they were modifying

Also, I do not know anything about the "Premium"-and higher version of JPD, so perhaps it has different administrative features.  Perhaps ping Atlassian (or your reseller partner) to learn more.