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

Moving closed issues in a BigPicture Roadmap

FredericV

Hello,

We've recently started using BigPicture in my company as we are implementing SAFe and need an online tool for our Program Boards. BigPicture Roadmap module does a very good job at that, but there are a few perks that could need improvement.

One of those is the fact that you can't move an issue in a Roadmap once it's closed (any "green" state). While I understand the logic behind the principle, it's actually not practicle at all as we're still adjusting our Boards, recreating or splitting them during the PI to make it easier to understand.

So my question is, are there any option available or planed to disable these kinds of rules ?

Accepted answers

Krisztian Kovacs_rapuo3

Hi @FredericV,

I don't know about switching it off but a possible workaround would be to created a new 'in progress' or 'open' type status, bulk transition all the issues while you are in this transition period.

You could still name it Done or Archived or Finished or something.

I know this could be a pain but I guess my main point is the bulk edit part. It depends, of course, how many closed issues you have as you have to do that in 1000 batches.

However in the end it might be useful to have a status before finally archiving an issue.

Let me know how horrible this idea is.

All comments

Krisztian Kovacs_rapuo3

Hi @FredericV,

I don't know about switching it off but a possible workaround would be to created a new 'in progress' or 'open' type status, bulk transition all the issues while you are in this transition period.

You could still name it Done or Archived or Finished or something.

I know this could be a pain but I guess my main point is the bulk edit part. It depends, of course, how many closed issues you have as you have to do that in 1000 batches.

However in the end it might be useful to have a status before finally archiving an issue.

Let me know how horrible this idea is.

FredericV

Thanks for the answer.

I've used such workaround, just by reopening the tickets I needed to move and then reclosing them once they were moved, but I fell it would be an improvement to the product to just give the possibility to disable such control.

Krisztian Kovacs_rapuo3

Cool,

then here you can reach them directly: https://softwareplant.com/jira/servicedesk/customer/portal/1

just sign up and you can add it as a feature request

FredericV

Thanks a lot

Ericka Samuels

I'm not too familiar with SAFe but , are you sure this is a limitation of BigPicture, and not of JIRA itself? Because on any kind of Board in JIRA, the states of the Board's columns/swimlanes are derived from the workflow engine set for the Issue Type. You wouldn't be able to do it via the JIRA interface either. You could ask SoftwarePlant to look at it, but , in some ways, they are just another front end on the JIRA entities, database, and workflow.

Apologies if I'm missing something that is a nuance of SAFe in BigPicture! In which case just tell me to be quiet!

Radosław (SoftwarePlant)

I can confirm that Ericka is right. If an issue is not editable in Jira it is impossible to edit it in our plugin either.

You may want to add a Quick Filter similar to:

"resolution is EMPTY"

to get rid of these issues or permanently remove them from Program scope by using extra filtering conditions.

I hope this information helps

Radosław of SoftwarePlant Team

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server