It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How do Jira Agile swim lanes relate to issue status in workflow?

With JIRA you have an issue workflow, and in JIRA Agile you have a different workflow (swim lanes)

How do the two workflows relate please?

5 answers

0 votes

Hi Dave,

Actually the swimlane is not a workflow, but  a horizontal categorisation of issues in the Active sprints/Kanban board on a board. Please check this page to have a detailed explanation on how Swimlanes work and how do it relate to the JIRA issues.

I hope it helps! smile

-- Arthur Gonçalves

0 votes

I think you've misunderstood swimlanes.  Workflow is a set of steps or status through which an issue progresses.  Agile allows you to map columns on to these (including the ability to have more than one status in a column, and not use the same names).  Swimlanes cut across these columns, grouping your issues together by something other than status.  Assignee, story, priority are obviously useful examples, but you can do almost anything with JQL.  (Including status/workflow, which would look a bit silly as all your issues would cluster into single row/column items)

Sorry for the delay, I am restricted in the number replies I can make in 24 hours.

Thanks for the reply Arthur and Nic. I still think I am confused. Would I be right in thinking that any swim lane change is not persisted with issue in any way, and that swim lanes just manage the life of the issue through the sprint?

I guess what is confusing me is that by default, there is a "Done" swim lane, and by default there is a "closed" status for an issue in Jira. These two seem like they are the same thing even though it appears they are unrelated.

0 votes

No, there isn't (unless you've done something really convoluted), you're still not looking at swimlanes. A swimlane goes across the board - they are *rows*, and they do NOT represent status (unless you've used JQL to make them do so, which is convoluted and pointless) A *column* is a column on the board. These represent the position of the issue in its lifecycle. In the back-end, JIRA workflow is a set of status that you move between. A board shows a set of issues grouped into columns by their current status. A column does not have to be named the same as the status it contains, and it can contain multiple status. So, you have a "closed" *status*, which appears on your board in the "Done" *column* (not swimlane, it's a column). They are not quite the same thing, as you could also have other status like "done", "ended", "rejected" etc in that column too. When you move issues between columns, it changes the issue status in plain JIRA.

We would like to measure movement between swim lanes if possible,  An example would be a story moved from to-do to development, then to UAT or SIT.  When UAT rejects it with a found bug, it moves back to Dev for repair.  We want to know how many times a given story moves back and forth between a testing state and a development state.  Has anyone seen a script or add-on that does this?

Sorry, didn't mean to post that here.

Hi Tom,

Would you be able to send a link to your new post please?

Or if you know of a way of doing this that would be great.



Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira Software

Metrics Fun: 2019 in Review

Hello, Atlassian Community!  I thought it would be fun to do something different for my teams' last retrospective of 2019 so I'm planning to do a "year in review" with info-graphics.  Wha...

1,545 views 10 13
Join discussion

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you