Feature Request: Audit Logging for Field Value Changes

[RehabAbotalep]

Select Topic Area

Product Feedback

Feature Area

Issues

Body

We’ve been using GitHub Projects and appreciate the flexibility of custom fields like single-selects, dates, and text fields. However, we've observed that changes to certain fields specifically built-in fields like Priority and Size, as well as custom fields such as Date Closed and Week Number are not being logged in the GitHub issue timeline or history. This makes it difficult to track important updates and introduces gaps in traceability.

Current Limitations:

• Changes to custom fields (like Priority, Size, Date, or text) aren’t logged anywhere.
• There’s no API or webhook support to capture when fields are updated, by whom, or what the values were before/after.

Why This Matters:

Being able to track field updates is important for:

• Transparency and accountability
• Workflow automation
• Compliance and reporting

Feature Request:

It would be extremely valuable to have:

1. Audit logging for field changes, including old/new values and timestamps.
2. API support (REST or GraphQL) to retrieve field change history.
3. Webhooks for field updates in GitHub Projects.

This would greatly improve project tracking and team collaboration.

Thanks!

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[slinna]

API support (REST or GraphQL) to retrieve field change history.

Yes, this would be very much needed!

[MohamedRadwan-DevOps]

Thanks @RehabAbotalep I do agree, we do really need this!

[crnnr]

I dont even understand how this was not implemented initally. Every other property in an issue has this changelog built in the issue.

[aburnettels]

This is exactly what my team is looking for. We would love to see this feature released.