Adding Multiple Swimlanes for Kanban/Scrum Approach

[Mark.Bonislawski]

This may be an unorthodox way of trying to achieve my madness.  I cant seem to properly configure swimlanes with custom queries. I'm trying to create multiple swimlanes 1 for each month. Such as "September", "October", "November" etc. What I want to do is utilize the "Due by" field I have on my Jira tickets so they appear on the teams Kanban board and know what upcoming work is available in the to-do column for that given defined swimlane.

So for the current month "September" I added a custom query "Due by" < endOfMonth() and assigned tickets with a september due date. Seems like it works fine. The moment I add "Due by" < endOfMonth("+1") to "October"  where things start to break. Tickets seem to not want to appear with October Due dates. When I switch it to Oct 4th due date then it appears the moment I add a week it disappears.

End Goal: Is to try and create a monthly view of planned/unplanned/inprogress/inreview/etc work within the kanban board.

[Inactive Stephen · Accepted solution]

Hi Mark,

This is how I did it with due date in our instance:

• Set due dates this month and next month. 
• Created two swimlanes - one for this month and one for next month.
• The first swimlane: duedate <= endOfMonth()
• The second swimlane: duedate <= endOfMonth(1)

^ This worked for me - so I tested it a second time with a new custom field I created, Due By. The only thing which changed was the search took into account a field with a space, so it was "Due By" <= endOfMonth().

It shouldn't matter if you put just a number, "+1" or "+1M" into the brackets. The number by itself should work as it defaults to plus when no parameter is given.

You'll also want to ensure you use "<=" to show the full month rather than prior to the end.

Alternatively, you could use dates (between 1st-31st October) - but I assume you want this to be a rolling board - i.e the top Swimlane becomes October past the end of September?

Let me know if the above helps solve the issue - if not, happy to try and assist further.

Ste

[Mark.Bonislawski]

Thanks for the advice. Something definitely weird is occurring because it pulls in tickets dated up to Oct 4th, however any tickets dated after the 4th do not appear on the board/swimlane. What could the issue be? 3rd Image shows the ticket dated the 4th and it appears exactly as expected. The moment the due date is changed it no longer appears. Same goes for any new/additional tickets assigned a due by date past Oct 4th.

Two Issues Discovered:

- Setting a "Due by" date of Sept 1st renders ticket to not appear on swimlane/board

- Setting a "Due by" date after Oct 4th renders the ticket to not appear on swimlane/board.

(Attached Screen Shots)

[Inactive Stephen]

What are the queries you have attached to each swimlane (just need the text)?

Ste

[Mark.Bonislawski]

September "Due by" <= endOfMonth()
October "Due by" <= endOfMonth(1)

[Inactive Stephen]

Strange - have you tried setting the columns based on dates (i.e after or equal to 01/10 and before or equal to 31/10) to see if this behaviour is consistent?

Ste

[Mark.Bonislawski]

I'm not sure I know how to set the columns based on dates. Can you explain/assist with this and I can try?

[Inactive Stephen]

* Swimlanes based on dates - so an example would be:

"Due By" >= 2019-10-01 or "Due By" <= 2019-10-31

If your Due By field is Date / Time you might have to add in the time also, such as:

"Due By" >= "2019-10-01 00:00" or "Due By" <= "2019-10-31 23:59"

Ste

[Mark.Bonislawski]

Both Work Now! I figured out what was wrong. The Project the board was created on was based off a custom JQL query. Filter Queryproject = DATAR AND "Due by" >= "0" AND "Due by" <= 4w

So it was only display within the 4 week timeframe. The moment I changed this to a generic project filter it resolved. Thanks so much!

[Inactive Stephen]

Awesome :) - glad I could help

Ste