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
Without having to download 3rd party apps. I would like to use a filter for when a custom field is updated but only when it is updated within 24hrs of ticket being assigned.
We have strict workflows and one specific field tracks if the customer issue has been resolved within 24hrs. Is this possible?
The CHANGED operator along with many of the HISTORY based operators are limited to only Assignee, Fix Version, Priority, Reporter, Resolution, and Status fields in Jira Cloud.
The closest you could probably get is an automation that set's the Resolution or a Status to the required value when the other field you are monitoring has a satisfactory value. Then make sure that either the Resolution or Status cannot be set in any other way besides filling out that specific field.
To filter Jira issues based on when a custom field is updated within a timeframe, you can use JQL (Jira Query Language) with the following syntax:
<custom_field_name> CHANGED DURING ("<start_date>", "<end_date>")
Replace <custom_field_name> with the name of the custom field you want to filter on, and <start_date> and <end_date> with the range of dates you are interested in. For example:
priority CHANGED DURING ("2022-01-01", "2022-12-31")
This JQL query will return all issues where the "priority" field was changed between January 1st, 2022 and December 31st, 2022.
Note that the date format must be in the format "YYYY-MM-DD" and that the date range is inclusive, meaning that issues where the custom field was changed on the start or end date will be included in the results.
@Hitesh This doesn't seem to work for custom fields. Have you managed to get this to work for a custom field ? It seems like it only works as per the docs say for these specific Jira system fields -> Note: This operator can be used with the Assignee, Fix Version, Priority, Reporter, Resolution, and Status fields only. (https://support.atlassian.com/jira-work-management/docs/jql-operators/)