Solved: Hi everybody, i'm evaluating JIRA Agile and i'm looking how i could group issues in swimlanes. I would like to group the issues of a. The only option that allows you to choose the order of swimlanes is when using " Queries". All the other swimlanes options are sorted out automatically by JIRA. Note that only the administrator of a board (or a person with the ' JIRA Administrators' global permission) can configure a board's swimlanes. Delete a swimlane Click the ' Delete ' button at the right of the swimlane. Linking issues Scheduling an issue Logging work on issues Editing multiple issues at the same time Moving an issue. How do I sort the backlog How do Story Points get burnt down and reflected on the Burndown Chart How-To Articles How to display the Sprint field in the quick Issue Detail View in Plan mode of Agile scrum board How to restrict the access to JIRA Agile Scrum board What are the permissions used in Agile Boards What if the JIRA Agile license count does not match with JIRA licensing Why do subtasks disappear when I filter my board using Epic Links. I don't know what your workflow looks like, but here's an example that comes to mind, say with three columns, each contating two statuses: One epic per swimlane, with issues that don't belong any to epics appearing below the swimlanes. Example click to enlarge: Assignees - this will create a swim lane for each issue that shows up on your board based on assignee 3. Change the JQL of a swimlane Click in the JQL area of the swimlane, modify the existing JQL and click the Update button. One epic per swimlane, with issues that don't belong any to epics appearing below the swimlanes. By the way Howard - Do you know if there is a feature request already open that I could vote on? Michael Brinson Oct 13, Yes No Thanks for britain s got talent feedback! By the way Howard - Do you know if there is a feature request already open that I could vote on? All I had to do was add a select-list custom field to the screens, and then set up swimlanes that filter based upon that field. No, I'm afraid you need JQL for each one. How are you determining what is "being worked on"? But I think thats the idea behind it. Even between sprints, you should not be adding new projects frequently. What I am looking for is a methodology that will allow me to replicate the 'waiting' concept that is part of Kanban.