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

Mothballed tasks appear in newly started sprints

Mark Diaper

Is there anyway of seeing previously mothballed user stories within a sprint before it is started? For three sprints now I have started a sprint and it then shows previously mothballed tasks.

If there is no way of seeing these before starting a sprint is there a way of removing these mothballed stories without impacting the burn down figures for that sprint?

Thanks

Mark

Accepted answers

Nic Brough -Adaptavist-

How are you indicating that an issue is "mothballed"? There's no functions for that in JIRA, so you need to explain what it means.

Also, a description of your board filter would be handy (or just the JQL!)

All comments

Nic Brough -Adaptavist-

How are you indicating that an issue is "mothballed"? There's no functions for that in JIRA, so you need to explain what it means.

Also, a description of your board filter would be handy (or just the JQL!)

Mark Diaper

parked.PNG

Hi Nic thanks for getting back to me.

I think what I was trying to explain was that when we "park" a story within a sprint candidate list (we have a number of sprints created before actually starting them) this is then removed from view within the list until we start the sprint when it then re appears. Is there a way of seeing these parked stories so that I can remove them from any of the existing created sprints? Is there a way of removing the parked stories from an active sprint without causing issues with the burn down figures?

parked.PNG

Nic Brough -Adaptavist-

Ok, that's a part of your workflow, so I assume you've got a status for "parked". What you're describing suggests that your board has a filter like "project = x and status is NOT parked". So the parked items are not part of the board.

What you're now asking for is "include issues in the board after deliberately excluding them". By definition, your board excludes them, so you have to look at them some other way. Run a filter for "status = parked" in plain JIRA, or create a new board that does not have "not parked" in the definition (I'd recommend a Kanban rather than scrum, so you don't get the complexities of multiple sprints that you probably don't need)

There's no way to remove them from the sprint without affecting the numbers because, well, they're part of the sprint.

Mark Diaper

Great thanks that has allowed me to filter out the parked stories so they dont appear in created sprints

perfect thanks

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud