Filter Subscription Misses Issues Updated Just Before Execution
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
When using a filter subscription with time-based conditions, there is a risk that some issues may not be included if they transition just before the subscription runs. This happens because the filter criteria might exclude issues based on precise timing.
Example: A user created a filter and set up a filter subscription that runs every 5 minutes using a CRON expression.
Filter example: project in (12345) AND Date1 >= startOfDay() AND Date2 <= endOfDay() AND Status changed to "specific-status" AFTER -5m
CRON: 0 */5 * ? * 1-5
Environment
JSW, JSM
Solution
Adjust the Filter Criteria:
To mitigate the risk of missing issues, consider slightly expanding the time window in the JQL query. For example, instead of using AFTER -5m, we might use AFTER -6m. This ensures that any issues transitioning just before the subscription runs are still captured. Yes you may get a any issue created in last minute repeated in the next email. But you would not miss any!
Alternative Notifications:
Add-a-custom-event - consider setting up a custom-event notification on the desired transition for required users.
If email subscriptions continue to pose challenges, consider exploring other notification methods, such as webhooks or integrations with other tools (such as Slack, Microsoft Teams etc) that might offer more real-time updates.
Was this helpful?