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
Is there a way to generate a report that gives me a list of all change tickets that were implemented in the last 24 hours and all the change tickets that are scheduled to be implemented in the next 24 hours? Also can this report then be emailed automatically?
Hello @Shanara Sadeque
Welcome to the community.
You can create filters in the Advanced Issue Search screen, save those filters, and set up subscriptions to the filters to have the results emailed to you on a schedule.
This page explains how to search for issues.
This page includes information on subscribing to saved filters.
Using this search functionality you can search for issues completed in the past 24 hours by setting a criteria for the Resolved field.
If you want to find issues that are scheduled to be resolved in the next 24 hours you would need to set a criteria for the date/time field where your specify the due date/time for the issue. In this example I'm using "complete by" to represent that field.
"complete by" > now() and "complete by" < 24h
You would want to add criteria to each of those for the Type of the issue and the Project the issue is in.
project = <your project> and Type = <change ticket issue type>
Thanks for the detailed explanation.
How do I construct a JQL that displays 2 issue types while also filtering the end date?
So I'd like the filter to show tickets with an end date in the last 24 hours with the issue type being either "standard change" or "CAB change"
Hello @Shanara Sadeque
You would add to your JQL a criteria to evaluate the issueType field.
It sounds like you would benefit from reviewing the documentation for issue searching.
You can switch to the Basic Search option:
And then use the options available to indicate you want to search for issues of specified types by check marking the types you want to include:
After completing that step
...you can Switch to JQL to see what the JQL syntax looks like: