📣 Product update: You can now copy project configurations!

[#1]

Hello everyone,

We know that onboarding new teams in Jira Product Discovery was not always easy, admins spend hours or days re-creating new projects. Manual project configuration is time-consuming and error-prone, especially when you have decided on specific guidelines and best practices to follow across your company.

We’d like to introduce a new feature: the possibility to Reuse a project configuration

This feature will copy all fields, views, idea types, workflows, permissions and custom roles (optional), allowing you to standardize key practices across your product organization.

Pro-tip: We recommend using global fields as much as possible to avoid field proliferation, per-project updates, and discrepancies between projects in the future. Learn more on how to transition from project-scoped fields to global fields.

To reuse a project configuration:

• Go to Create project > Product Management.

• Select Reuse a project configuration.

Read the full documentation here

Check out this full feature demo (with few advice for admins )

We hope this feature will be a first step in an easier adoption of Jira Product Discovery at scale - In future iterations we will add more such as idea templates or access settings. In the meantime, don’t hesitate to drop feedback or questions in this community post.

Cheers,

Hermance

[scuryova]

Woohoo! 🥳

[Tomislav Tobijas]

Lovely! 🤩

So, when's this coming to all other Jira products/apps? 🙃

[Gunnar Gylfason]

I have a couple of questions:

1. Anything you can tell me about this error I'm getting when trying to copy my JPD configuration? FYI this was solved by support

"errorMessages": [
"[field: Invalid searcher chosen for custom field. Invalid configuration for PCRI: pcri:field:ref:customfield_12177,...

2. Given that I can get this to work, do you have any suggested ways of working so I can move all existing ideas from one JPD to this one? So to provide context, what I'm trying to do here is basically duplicating my project, so I can clean up redundant fields, workflows and views as well as implement the new types without risking ruining the currently live (and very important to us!) JPD project. 

[Yiling Baldez]

@Gunnar Gylfason - did you ever find an answer? Struggling with the same thing right now. 

[Gunnar Gylfason]

@Yiling Baldez ish. I ended up not using this new functionality because project configurations don't copy permission sets, and they can't be configured in JPD projects so my plan of using Deep Clone, a third party app I wanted to use to populate my new project, wouldn't work (although it works in a 'normally' created project). So, I manually recreated all of the most relevant fields and values, exported everything to CSV and then imported what I could via csv. 

Still resulted in a lot of manual work since many of the columns didn't upload correctly, e.g. had to manually put everything into the correct roadmap bucket etc. 

Not quite what I was hoping for, since I don't want to go through this process again but it got me there at the end. 

The other solution I tried is to create a sandbox environment of Jira and populate JPD with prod data.

[Hermance NDounga]

Hi there, I wanted to let you know that this feature now brings permissions and custom roles!

[Seth Hunter]

@Hermance NDounga  Thanks for this overview, very helpful and a much awaited functionality! Follow-up question; is there a way to apply a "template Project" to an existing JPD project? or is this functionality only able to be used when creating a new JPD project?

[Gary Spross]

@Hermance NDounga, I ran into an interesting issue when using the product copy feature today. I copied from a project that has it's access set to private. I also selected an Access level of private in the create project options (as it's required). The project was then created, but I'm unable to access it. I'm listed as the lead for the new project (since I created it) and I am able to access the project I used as the template, so it seems very odd to me that I'd be unable to access the new project. I wasn't sure where the best place to report this was as I would think this is a bug.