nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can I set issue types for ALL project types?

Sebastian Mühleis_22qeil

Hello community :-)

Even though the issues "epic" and "story" are not typically part of a classic business project, I'd like to include all standard issue types (epic, task, subtask, story, bug) automatically in all new project, even in the project types under "Business Project". Does anybody know where I can preset this?

Thanks in advance for your help,

Sebastian

Accepted answers

Stuart Webb_an62p9

You can create template project, then when you create a new project, you can copy this existing one and it will have the same setup and re-use the issue types scheme

All comments

Stuart Webb_an62p9

You can create template project, then when you create a new project, you can copy this existing one and it will have the same setup and re-use the issue types scheme

Sebastian Mühleis_22qeil

Hi Stuart,

thanks for your answer. I saved a new template (and renamed it) where I included all issues. But I can't find this template directly WHEN I create a new project - I only find it AFTER I created a project. Could you help me out where I make a mistake?

Thanks in advance (again),

Sebastian

Stooz

It sounds like you want the same issue types on all your projects?

What you need to do is create an issue type scheme (you probably have the default one)

then re-use that on any project you create.

To make it easier for us, we create a project called "baseline" then when we create a new project, we click the option right at the bottom of the modal "use a shared configuration" - choose baseline as the one to copy, and give it a new project name.

Then this new project will be using the same share issue type scheme as the baseline one.

Sebastian Mühleis_22qeil

Hi Stooz,

thanks for your input. I already created an issue type scheme, renamed and saved it. But I was looking for the part you described when creating a new project. We're setting up a new Jira & Confluence environment for our team, so it's a good idea to use a (probably closed) project as model project for the new ones.

So thanks again for your help.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

issue

cloud

jira-software

automation

issue-type

configuration

default