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

Cloning simplified workflow to add columns broke status transition

boardtc

In the ticket I cloned the standard workflow to added 2 columns: Review & Text. The goal was for the workflow to work exactly the same otherwise.

This workflow is live and today a user has reported an issue with the workflow which I have tested and confirmed - Jiras moved to done are not being marked as status Done - here's the status after moving:

Consequently the burndown is affected,

When I edit the 2 new status the category is In Progress, is this correct?

In the previous ticket it was mentioned that I need to "require the Resolution in the transition to Done status", I'm unsure what that means?

Somehow in cloning the simplified workflow a bug has been introduced.

Opening up the Done All transition, I see:

edit to done.png

Any thoughts appreciated.

Accepted answers

George_Stan

Hi Tom,

In order to get it closed you need also to set the resolution, so you can edit the last transition, from TEST to Done, and from the Post functions, you can select " The Resolution of the issue will be set to Done" or you can chose a different resolution also: resolved, fixed, etc.

All comments

George_Stan

Hi Tom,

boardtc

George, my apologies, I posted the wrong workflow screenshot above and have updated it now, I have no transition from Test to Done.

Nic Brough -Adaptavist-

Yes you do. There is an "all" going into Done.

boardtc

Thanks Nic, didn't realise we were counting all as specific transition.

Opening up the Done All transition, I see:

edit to done.png

The other all transitions, are similar.

@George_Stan How do I see these post functions?

Welcome!

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

Quick Links

Find more posts tagged with

jira-software