-
Suggestion
-
Resolution: Unresolved
-
None
-
8
-
55
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Hi everyone,
Thanks for voting and commenting on this issue.
This capability is now available using the new "Create project with shared configuration" feature, which was released to all versions of JIRA at the beginning of October 2015 (JIRA 7.0). When creating a new project, simply click the "Create with shared configuration" link in the bottom-left corner of the dialog, choose an existing project, and a new project will be creating that shares the same workflow scheme (and other schemes) of the existing project. More documentation is available here.
We recognize that this is not exactly the same as setting a workflow scheme as "default". Simplifying project setup, configuration, and maintenance is one of the JIRA team's top priorities right now. We are in the early stages of a big investment in making it easier to get started with a JIRA project and maintain a large number of projects at scale.
We will continue to work in this area and intend to provide more comprehensive support for this in the future.
It's important to understand that we rarely try to implement individual features from jira.atlassian.com, but instead take a holistic look at the problem and use feedback from the comments here and a dozen other sources of customer input to solve the core problems.
Please don't hesitate to contact me if you have any questions or feedback.
Regards,
Dave Meyer
dmeyer@atlassian.com
Product Manager, JIRA Platform
We have set up a custom workflow scheme that we'd like to use on all new projects.
We need to specify that this custom scheme should be used by default for new projects – without explicitly specifying it on Administer Project page.
Alternative solution would be to have Workflow Scheme selector right at the Create Project screen, so that admins have a reminder that it should be specified in some way.
- is duplicated by
-
- Closed
- relates to
-
- Gathering Interest
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page
Failed to load
-
Page Loading...
-
[JRASERVER-9363] user-defined workflow scheme as default for new projects
Dear Atlassian, can you please give an update on this feature request? It's been 4 years since your last update...
I don't understand why this issue is still considered "Gathering Interest" if Atlassian has decided that the current functionality is sufficient. It should be closed if they don't intend to implement it.
Quite shocked it's still in the works. Seems like an obvious feature for people who want to keep Jira tidy and have a couple of workflows (custom) they always use. Right now I need to manually switch a workflow schema and then go into settings to delete a default workflow that was created automatically. This is rather annoying.
I just had to clean up 12 projects that were created by a new team and change out the workflows for every single one of them. This is what I got to do on my Friday night when the issues were coming in with only 3 states.
This problem has been reported since 2014, that is 6 years and the solution is to teach new users a way to create a 'shared configuration'... I don't get it. Jira is a GREAT tool. Not an okay tool but a GREAT tool and the users are Excited to use it. However, when we trip over these kinds of manual stupid things we have to work around, it just makes it tough to administer to make it easy for the users.
Please work on good simple bulk solutions for people who have to administer the system and not spend an hour making a series of changes manually. Don't push the burden to the users, provide the right tools for the people who administer it.
Shared configuration is not a solution but a workaround, and a pretty sloppy one. Come on guys, it can't be that difficult to add such a basic functionality.
@james leighs:
We've solved this by having a project we use only as a template for each project setup. When creating a new project, we do it with a shared configuration - that ensures that all settings are correct and we only have to change a few things, like project type, owner, etc. on project creation.
Upvoting this - we use Jira as part of our QMS and need an easier way to ensure users always start a new software dev project with our in-house default workflow for dev projects.
This is such an inconvenient solution. There is never a "clean" version of the workflow one wants to use when creating new projects. Any modifications made to the workflow under the existing project are inherited to the new project with the shared configuration.
I'm trying to implement a proper workflow pattern for my process and I haven't succeeded yet. Every inclusion of a new project I have to change the workflow. Other tools already have this.