Skip to main content

Jira workflow for new projects

Associated workflow creation

I'm a Jira Cloud user and begining from some version 6, I noticed that when I create a project, it automatically creates a Workflow and Issue Scheme that is prepended by the project key and which is a copy of the default scheme.

I always had to make a cleanup after creating a project.

Default workflow for new projects

I also miss a feature that would allow me to make a custom workflow (and globally custom project setting) the default for new projects I create.

Solution: Create with shared configuration

While searching, I noticed that with Jira Cloud which is version 7.1.0 at the time I write, there is a link at the bottom of the "Create project" wizard:

"Create with shared configuration" will allow me to select the project I want the new one to share configuration with.

  • The new created project will use the same configuration as the project I select
  • There will be no creation of Workflow and Issue Scheme that I need to cleanup


This feature is a solution to the reported issues:

  • https://answers.atlassian.com/questions/150807/how-can-i-change-default-workflow
  • https://answers.atlassian.com/questions/45156/how-do-you-change-the-default-workflow-to-a-custom-one

Also having a Jira 6.4 Hosted, the dialog is a bit different and unfortunately what I avoid is only the creation of Workflow and Issue Scheme. I have to click on "Jira Default Schemes":

The new project will have the default configuration that I will have to manually change, but no Workflow and Issue Scheme will be added to the system.


Comments

  1. I had Created a Project on Jira. It has Created a Default workflow.Later on It is decided that Proper workflow should be assign to that project. I had Created Workflow.Now I am in confusion that If I edit in Default workflow all the Issues that are created in Default workflow also moves with new workflow

    ReplyDelete

Post a Comment

Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='https://ngx.rktmb.org/foo' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href='https://ngx.rktmb.org/foo'" parameter. npm run build --base-href='https://ngx.rktmb.org/foo did not set the base href in indext.html After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='https://ngx.rktmb.org/foo&

dockerfile multiline to file

Outputing a multiline string from Dockerfile I motsly use a Dockerfile by sourcing from a base ditribution: CentOS or Debian. But I also have a local mirror and would like to use it for packages installation. Espacially on CentOS it is about many lines to write to the /etc/yum.repos.d/CentOS-Base.repo file. Easiest way: one RUN per line The first method that comes in mind is to issue one RUN per line to write. Here you are: RUN echo "[base] " > /etc/yum.repos.d/CentOS-Base.repo RUN echo "name=CentOS-$releasever - Base " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "baseurl=ftp://packages-infra.mg.rktmb.org/pub/centos/7/base-reposync-7 " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "gpgcheck=0 &quo