due date change details

[Nidhi singh]

Hello All,

Can anyone know how we can identify all ticket in which due date has been changed? I checked their is no JQL query which can fetch all ticket in which due date has been changed means not that which was set as an initial.

If JQL is not their except any addon do we have any alternate option to track that?

Thanks

[Pears Whims]

Hi @Nidhi singh ,

I just wanted to check in and see if any of the suggestions from the community helped you resolve the issue of tracking due date changes. If you’ve found a solution, feel free to share or accept one of the answers. It helps others in the community find the right solution quickly.

Let me know if you need any further assistance!

Best regards,
Pears

[Pears Whims]

Hi @Nidhi singh ,

Just checking in to see if any of the suggestions from the community helped you resolve your issue with tracking due date changes in Jira.

If you found a solution, it would be great to know - especially if you’d like to accept any of the answers, as this helps others find solutions faster.

Let me know if you need further assistance!

Best,
Pears

[Pears Whims]

Hey @Nidhi singh

JQL does support the was function, which may meet Your needs for tracking due date changes

And on this topic You may find this thread helpful: https://community.atlassian.com/t5/Jira-questions/Is-there-a-way-to-find-Jira-Issue-Due-Date-changes/qaq-p/1968959

In this thread, various approaches are discussed, including:

• Using the built-in Jira history to manually check changes on individual issues.
• Exploring third-party add-ons like “Issue History for Jira” for more comprehensive tracking and reporting.
• Leveraging REST API scripting for more customized solutions.

These suggestions should give you a better idea of the options available.

Cheers,
Pears.

[Trudy Claspill]

Hello @Nidhi singh 

Without a third party app you have one option for finding information about issues where Due Date has changed at some point in the past - use the Jira REST API to retrieve issue change log information and parse through the logs looking for the information to indicate that Due Date was changed.

A go-forward solution would be to use Automation Rules to make a note in a custom field in each issue about the Due Date being changed. That rule could keep a simple tally of the number of times the field has been changed, or you could use a text field to keep track of the details of each change. You could then use JQL to search for information based on that custom field.