How to set de desfaults for a new project on jira cloud?

[DALI DAVILA]

I know this has been asked many time before, but, not sure if there is a new answer overthere.

The idea is that when a user creates a new project, that project get created having specific configuration setted, like, permissions schemes, workflow schemes, issue type schemes, etc.

One option is to use a project template with all that things setted and then use the option "shared configurations with an existing project" when a new project have to be created, but beeing honest, that represents a challenge, first because we have to be sure that every person know that insight, and on the other hand, there is many "creative" persons overthere. 

I know, in a mature environment people could and should be allowed to sugest new aproaches to make anithing, but our case is not that, we are just starting to use Jira and to have some basic options for now.

Other option we was thinking was using the new automation rule engine but we didnt see any option for that there.

Any new Ideas to share? Thanks a lot in advance

[John Funk · Accepted solution]

Hi Dali - Welcome to the Atlassian Community!

You're description above is very spot on. There is nothing new on the horizon to solve this that I am aware of. 

[DALI DAVILA]

Thanks for your Reply @John Funk 

[DALI DAVILA]

Hi @John Funk  !!

I was messing around with permissions schemes and I found a way to make that at least the default permissions scheme changes for every new project created, I dont know if this was obvious but wasn't for me that's why I want to share it.

There is a "Default Permission Scheme" that exist on a new instance of Jira Cloud. That Scheme seems to be just a "preview" of how the default permissions in jira looks like, because if you modify that scheme and create a new project that new project doesn't heritate that scheme, actually what happen is that a new scheme is automatically created (Default Software Scheme) with exact the same permissions that the "Default Permission Scheme" had originally, even if you change that scheme (Default Permission Scheme) the new one is created with the original permissions.

Now, if you modify that new scheme (Default Software Scheme) to your needs, and then create a new software project, that new project does heritate, or better said, associate the Default Software Scheme to that new project with all the changes that you have made to that scheme.

This is helpful for us because we dont have to associate manually a permission scheme to every single new project.

Hope it helps to someone in the future.

CY!!

[John Funk]

That's fantastic, Dali! Thank you for your persistence in finding a work around!