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; } } }

Is there a way to promote issues defined in a project to an issue scheme (or global issue)

andrew_ojsyjc

I created a project and defined a bunch of issues. I need to create a workflow, but I can only define a workflow in terms of globally defined issues (the ones from my project aren't available when I try to define a workflow).

My goal is to define a workflow in terms of the issues that I've already defined in my project. Can I promote my issues to being globally available?

Accepted answers

All comments

Nic Brough -Adaptavist-

Workflows do not belong to issues or issue types directly, and there's no such thing as "globally available" because all workflows, issue types, schemes, and so-on can only be "global", there's no way to make them anything other than global.

I think what you mean is that you want your project to use your new workflow for certain issue types that the project uses.

To do this:

Create your new workflow
Create a new workflow scheme, one that associates your new workflow with the issue type(s) you want to follow that workflow
Change the project, selecting the new workflow scheme in the settings

andrew_ojsyjc

I think I'm missing something.

I have defined a new type of issue in a project, with different fields and a different name. I can't see that issue when I try to create a workflow.

Nic Brough -Adaptavist-

I don't understand why you think you need to see an issue when creating a workflow, they have nothing to do with it.

Go to the list of workflows, and click "create". You will get a skeleton workflow which you have to name and then (optionally) edit and save. It has nothing to do with any issues at that point.

Could you explain why you think you need an issue to create a workflow?

andrew_ojsyjc

I found this forum thread on how to assign workflows schemes to projects. I am having the same problem, so maybe my problem is actually stemming from a different misunderstanding.

My use case is that I need to be able to define rules for when an issue can be moved to a particular (custom) status based on that issue's field values.

Also I found this statement:

Associating a workflow scheme with a project
You can associate a single workflow scheme with more than one project, although only one workflow scheme can be associated with a given project. The issue type scheme associated with a project defines the issue types that are available to that project. If an issue type is not defined in the project's issue type scheme, its workflow is not used.

In the Managing your Workflow document

So, if I understand this correctly, I need to create an issue type scheme outside of my existing project for a workflow to be useable?

Welcome!

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

Quick Links

Find more posts tagged with

agile

workflow