Can I transition issues without moving them through a Sprint Board?

I'm aware of some "heavyweight" answers to my question.  I'm hoping to find a lightweight answer that requires only a single JIRA project.

Many issues make it into a Sprint.  But not all do, even though they are worthy of discussion.  For the latter we want allow detailed discussions with folks who are not part of the development team. And we want to be able to simply transition them to the "Done" state without ever including them in Sprint planning, preferably in a basic issues view.

Apologies if I'm missing something obvious but I don't see a way to do this. I can see the status in the right hand panel but I can't change it by clicking on a pencil icon the way I can other fields.

I realize this is not especially rigorous Agile but we don't need especial rigor for some of our projects.  Some core teams are small and team members wear many hats.  We don't want or need another JIRA project (Software of Service Desk) to carry out and track discussions with folks who aren't part of a development team.



4 answers

0 votes
Warren Levy Community Champion Oct 03, 2017

Hi Greg

You can set up the workflow so that any state can transition to any other state, then you could drag an item from the very left hand column directly to the very right hand column.

But ... that would apply to all issues not just the ones that are your "special cases". If you can live with that, it's a simple solution.

0 votes

Hi Greg,

Warren has said almost everything with the information you have provided. 

For an exact answer you would need to describe an exact need, because there are many approaches possible.

0 votes

There's no harm in taking an issue from backlog straight to done without going through a sprint.  Think of the cases where you are grooming a backlog and think "hang on, this one is a duplicate/won't do/misunderstanding" - those go to done without any work

The most simple trick would be to have a transition that allows you to go straight to done, either from the beginning of the workflow, or from any point within it.

A second option might be to have a dedicated issue type for these exceptions, then you could have a different workflow for them.  Or, you could put a flag field on the issues to say "this is an exception", and then stop it moving through the workflow by putting conditions on it saying "only if exception flag set/not-set"

First (duh), permissions. I have multiple accounts with different permissions for testing.  I was using the wrong account.  With the correct permissions I see work flow states in the issue dialogue and I just click to change.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

863 views 3 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you