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

Hi, How can i create a workflow that has two beginnings ?

unknown

I have an two types of issue- Adhoc bug and Bug analysis. The bug analysis has a 3 steps and should then flow into the workflow for Adhoc bug or can directly be closed. How can I do that as I am not able to transition the end of one workflow into the beginning of another workflow, nor have two beginnings within the same workflow.

Accepted answers

Nic Brough -Adaptavist-

You can not do this, as it is nonsense. When you create an issue, it has to know what state to create it in, it makes no sense to say "I create an issue in a state that is totally undefined"

But you can have different status by issue type - it does make sense to say "bugs start as 'needs investigation' while new features go start as 'have a chat with people'"

To do this, use different workflows. The workflow scheme tells Jira what workflow to use for each issue type in the project.

All comments

Nic Brough -Adaptavist-

You can not do this, as it is nonsense. When you create an issue, it has to know what state to create it in, it makes no sense to say "I create an issue in a state that is totally undefined"

But you can have different status by issue type - it does make sense to say "bugs start as 'needs investigation' while new features go start as 'have a chat with people'"

To do this, use different workflows. The workflow scheme tells Jira what workflow to use for each issue type in the project.

unknown

Hi, Maybe I can explain the situation a bit more. We have bugs raised through our service desk that come to the Business Analysts to do some initial analysis. This will have two steps-> High level analysis and then either closed or ready for Dev to do some work. If it goes to dev, it follows the usual process of coding->testing ->complete which is a workflow by itself. The issue i'm having is that I am not able to change issue type. If i can, then I can keep them as seperate workflows and change the issue type. If i cannot, is there any other way to for the above situation?

Milan Chheda [INFOSYSTA]

In this case, when issue goes to "Ready for Dev", I would rather create another issue under issue type 'Bug' and link that to original issue that was raised through service desk. This would ensure you have separate workflows and no need to change issue types too.

A separate workflow gives you more flexibility and control. Also, you can update main issue based on linked issues using post functions.

Changing issue types is never recommended, as far as I know, because every issue type has it's own workflows, screens, fields configurations, etc.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-administration

workflow