Shared Workflow across JPD Projects?

[Patrick Chen]

Is there any intention to allow Workflows and other configurations to be shared across JPD Projects? Seems like a no-brainer coming from vanilla Jira not to have this. I am preparing to spin up no less than 12 JPD Projects but now I have to manually create the Workflows and Field configurations 12 times. 

[Kamila Czubaj · Accepted solution]

Hello, you can use the following features to make that easier:

• Use a space as a template to create other spaces

For that you need to use global fields

• You may need to convert existing project fields to global fields
• and you can copy field values using bulk edit

How do I copy field values between 2 fields? 

If you want to copy values between 2 fields in the same project (for example to move from a select field to a multi-select field) , you can use the "bulk edit" functionality in list views:

Demo: copy field values using bulk-edit.

If you are already using a Project Field in a project and you would like to use a Global Fields instead: you can use the “Copy Values” feature which helps you copy field values for all Ideas in a project from a Project Field to a Global Field.

More info and demo for Copy Values here.

And the documentation.

[Patrick Chen]

Custom Space Templates is a feature locked behind Jira Enterprise?

[Kamila Czubaj]

Yes, Custom Space Template is a Jira Enterprise feature.

But this is a different feature from the one I am referring to for JPD, "Reuse an existing space configuration".

[Gary Spross]

The ability to reuse an existing space configuration is helpful, but it doesn't solve the issue of having multiple JPD spaces and keeping their configurations in sync after the spaces have been created. Most notably the applied workflows.

The global fields feature is also very useful, but again, doesn't solve for the bigger issue of space admins having the ability to create space level fields. Implementing standardized configurations means this can't be allowed. Since the "Administer project" permission is all-inclusive, there's no way around this.

It would also be great if, like Jira & JSM, JPD utilized the existing permission schemes. Then the existing defined roles could be utilized as well as the defined, standardized, permissions. The necessary additional permissions (managing views, managing delivery, etc.) could be added to the existing permission schemes. In fact, when JPD was first introduced a bunch of permissions where added (and still exist within) the permission schemes at the bottom in a section called "Other permissions". I had hoped this meant Company-managed JPD spaces were on the roadmap...

Oh and lets not even get started on having the ability to provide screens. The "Create ideas" area within JPD space settings is not good. Not being able to specify fields explicitly, but instead having to align the Create screen to a view is illogical. Not being able to specify required fields or contexts for fields... Not to mention the fact that clicking the main "Create" button provides a different experience for the user then when clicking the "Create" button within a view.

My point is that having the ability to create JPD spaces using the Company-managed style would solve for this existing issue of not being able to standardize configurations within JPD. Instead, we are getting additional configuration mechanisms that solve bits and pieces of the overall issue.

[Gary Spross]

Tell me about it... I would very much appreciate if Atlassian would roll out an update to allow the creation of JPD spaces in the company-managed style to allow for standardization of configurations. The scalability aspect is so necessary.

[Joni Johnson]

@Gary Spross That would be helpful to be able to have standard JPD configurations for the organization.