Hi everyone,
I need help creating a Jira Automation rule for expiry reminders in my Proposals project.
I have:
I need notifications sent to:
Reminder schedule:
After the expiration date, Jira should send daily reminders until the issue status changes to:
Thanks in advance for your help! 😊
Hello @Aleksandra Sobusiak
I suggest this approach
Trigger
Scheduled trigger running once per day with JQL :
project = "Proposals" AND issuetype = "Licences" AND status NOT IN ("Closed Won", "Closed Lost") AND cf[10986] IS NOT EMPTY
Conditions - If / Else with Work item fields condition and time frame
You can also use jql condition like cf[10986] = startofday(21) for 3 weeks etcc
Action
Send an email notification to user picker field
Hope this can help
This is one way that should work for you but please test it out.
You could use JQL to find these as well.
I would only add myself to the email for now and then test this out on a test ticket by adding a condition that is specific to the test ticket. You can manually kick off a 'Scheduled trigger' automation by clicking the 3 dot menu in the top right corner next to 'Return to rules' and then select 'Run Rule'.
Hope that helps
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Aleksandra @Aleksandra Sobusiak -
Both approaches above are solid and will work. One thing worth flagging before you
build it out as a single rule with 5-6 branches: Jira automation rules have a limit
on the total number of components (trigger + conditions + actions) - 65 in one
rule. With 6 branches (4wk, 3wk, 2wk, 1wk, 1day, post-expiry) each running a
condition plus an email action to three recipients, you can get closer to that
limit than it looks, especially if you ever add more intervals later.
If you want to sidestep that entirely, splitting into 6 separate scheduled rules -
one per interval, each with its own simple JQL and one email action - is a bit more
setup up front, but each rule stays small, and the Audit log for a single-purpose
rule is much easier to debug than tracing which branch fired inside one big rule.
Either way, Alan's @Alan Bruce tip about manually running the rule on a test ticket first is
the right way to validate the timeframe conditions before it goes live on real
Licences issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.