You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have created an automation to assign the due dates to an issue automatically based on the priority once an issue is created.
But now I am looking a way to automate the process of changing the issue swimlane based on the due date. Idea is to change the swimlane once the due date is passed.
Just following up to check if you solved this by modifying the rule, or if you needed other assistance.
If this not solved, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas. Thanks!
Yeah, you can easily do this with something like the following example ....
I often colour-code the cards in a similar fashion based on how late the get.
You could have multiple swimlanes based on how late they are ...
duedate < startofDay(-5d)
However, remember swimlanes will need to be order of longest to newest to prevent them always matching against the first item.
I hope this makes sense.
Columns are based on the current "status" of the ticket.
You could create a status called "Late" and automatically move tickets to that status when the curent date has gone past the due date. However, that's probably not good working practice and gives a problem of where does the ticket go if/when the due date gets updated to be another date in the future.
Swimlanes would definitely be my recommended approach (and probably colour coding cards based on lateness too).