Filter by duedate in specific month

[Rune Rasmussen]

Hello

Situation

I am trying to create filters that shows tickets with the duedate set for a specific month.
So if the duedate is set to the 25th of January, no matter the year, I want my filter to show it.

Purpose

The filter will be used for swim lanes in a Kanban board, allowing a team to get a quick overview of the epics (or whatever issue type they desire) that are due within a given month in any year.

My findings so far

So far I've only been able to filter dates within a specific year, with something like duedate >= "2021/01/01" and duedate <= "2021/01/31"
This would require someone to go and change the filter for all 12 swim lanes whenever a new year comes around.
Not quite the sexy solution I'm hoping for.

Alternatively one could use something like duedate <= startOfYear(31d) to get anyhting created within the first 31 days of the current year (January), but this becomes an issue if/when something due in December hasn't been finished yet, and is now not visible in the swim lane anymore.

Questions

Can I do what I want to do with any built in features?
Is it in any way possible to filter dates using wildcards?

[Bill Sheboy · Accepted solution]

Hi @Rune Rasmussen 

One way to do this with out-of-the-box features is to use an automation rules to extract the month value, for example into a label or custom field.  And then you may filter on it easily.

You will need two rules: one triggered on issue create and another in case the due date changes.  For example to do this with a custom field, the create rule would be:

• trigger: issue created
• action: Re-fetch (this slows down the rule and prevents racetrack, timing errors)
• if/else: condition, due date is not empty
  • action: edit the custom field, extracting the month from the due date
• else
  • action: clear the custom field

You will need a copy of this rule, with a different trigger, to handle changes to due date.

To get you started here is some documentation and examples of rules.  And if you get stuck, please post your rule and the community can help.

• https://www.atlassian.com/software/jira/guides/expand-jira/automation
• https://www.atlassian.com/software/jira/automation-template-library#/ 
• https://community.atlassian.com/t5/Automation-articles/Jira-Automation-all-the-resources-you-need-in-one-page/ba-p/1388465

Kind regards,
Bill

[Rune Rasmussen]

Ahoy Bill

Your pointers helped me get it working, that you very much.

Here is the rule I made, in case someone else runs in to similar issues in the future:

Rule overview

When the value of Due date changes, for all operations (saves me the trouble of having two similar rules, one for creation and one for changes)

I made a custom field (Type: Labels), and it gets set as the month of the year that the due date is in.
{{issue.dueDate.monthOfYear}}

It is set as a numerical value, so January = 1, February = 2, and so on...

Bonus info:

Since my custom field is being edited every time the due date is set/changed, it is hidden from the view through the Issue Layout settings in the relevant project.