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

Why does my subtask get cancelled instead of closed

María Morillo- Velarde

My project workflow has included (in the board configuration) both status (closed and cancelled), but in the "active sprint" tab I'm just able to move US and sub-tasks to the "cancelled" one, not giving me the chance to choose. Can anyone help me, please?

Accepted answers

John Funk

Hi Maria - Welcome to the Atlassian Community!

Check the transition to Closed in the workflow to see what Conditions might be on the transition which would cause it not to show up.

All comments

John Funk

Hi Maria - Welcome to the Atlassian Community!

Check the transition to Closed in the workflow to see what Conditions might be on the transition which would cause it not to show up.

María Morillo- Velarde

Hello John! Thanks for your replay.

I've included some screenshots of the Workflows which US and ST follow. Some of the status are not currently configured in the Board columns.

In case of User stories we begin with Backlog -> Ready to develop -> Developing -> Closed, having blocked and cancelled available from each of them.

For subtasks: Open -> In progress -> Closed (+ reopened, cancelled and blocked accessible from each of them).

Can it be the problem? Should US and ST pass through every status available in the pre-defined workflow? Subtask WF.jpg User story WF.jpg

John Funk

You have to click on the transitions between the statuses - the lines - to get a popup box on the right side that will give you access to the Conditions.

María Morillo- Velarde

I'm just able to see the workflow, but not to interact with it. No click, no pop-up box

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

workflow

status