Missing timeline of all events happening on a project card

[Fgerthoffert]

Select Topic Area

Product Feedback

Feature Area

Projects

Body

Today, the timeline on issues provides a view over the events over the issue fields, but this feature is not available for the timeline of events on project cards.

Most existing discussions (such as https://github.com/orgs/community/discussions/143179) seem to focus on the card status, but this type of information is also very much necessary for all other fields added by the user.

Workaround using webhooks (far from ideal)

Interestingly, this data is currently available via webhook and the projects_v2_itemevent type in the "changes" object.

For example, an archived card:

    "changes": {
      "archived_at": {
        "from": null,
        "to": "2025-03-06T12:15:40Z"
      }
    },

Or a single-select field:

    "changes": {
      "field_value": {
        "field_node_id": "PVTSSF_lADOAArxx84Aunb9zglLsWY",
        "field_type": "single_select",
        "field_name": "Priority",
        "project_number": 31,
        "from": {
          "id": "b80f6e5b",
          "name": "Next Week",
          "color": "ORANGE",
          "description": ""
        },
        "to": {
          "id": "1d36a1ea",
          "name": "Now",
          "color": "RED",
          "description": ""
        }
      }
    },

So we ended up using webhook listener that dumps all these events to an Elasticsearch instance, we then re-build an object with additional metadata (the repo, the source PR or Issue), and can generate such views:

Issue: Issue title (#89) 
Repository: org/repo
Last updated: 2025-03-05T14:15:51.638Z 

List of events performed by users: 
|----------------------|-----------------|-----------|------------------------|-------------------------------------------------------------------------------------------------------------------|------------------------------|
| Date                 | Who             | Action    | Project                | Change                                                                                                            | Event ID                     |
|----------------------|-----------------|-----------|------------------------|-------------------------------------------------------------------------------------------------------------------|------------------------------|
| 2025-03-05T08:52:45Z | user1           | edited    | Team - TEAMA (#37)     | Modified field "Status": In Progress => Blocked                                                                   | PVTI_lADOAArxx84Avkz4zgXbG9s |
| 2025-02-28T13:36:21Z | user1           | edited    | Team - TEAMA (#37)     | Modified field: "Linked pull requests"                                                                            | PVTI_lADOAArxx84Avkz4zgXbG9s |
| 2025-02-28T13:36:21Z | user1           | reordered | Team - TEAMA (#37)     | {"previous_projects_v2_item_node_id":{"from":"PVTI_lADOAArxx84Avkz4zgW58C0","to":"PVTI_lADOAArxx84Avkz4zgW58DQ"}} | PVTI_lADOAArxx84Avkz4zgXbG9s |
| 2025-02-28T13:36:21Z | user1           | edited    | Team - TEAMA (#37)     | Modified field "Status": Todo => In Progress                                                                      | PVTI_lADOAArxx84Avkz4zgXbG9s |
| 2025-02-28T13:31:33Z | user1           | edited    | Area - Tech (#23)      | Modified field: "Linked pull requests"                                                                            | PVTI_lADOAArxx84AsjEgzgW8eK4 |
| 2025-02-28T13:31:33Z | user1           | edited    | Another Project (#50)  | Modified field: "Linked pull requests"                                                                            | PVTI_lADOAArxx84AzSgRzgXzZwU |
| 2025-02-28T10:34:21Z | user2           | edited    | Another Project (#50)  | Modified field "Team": null => 🐐 TEAMA                                                                            | PVTI_lADOAArxx84AzSgRzgXzZwU |
| 2025-02-28T10:34:16Z | user2           | edited    | Another Project (#50)  | Modified field "Priority": null => Now                                                                            | PVTI_lADOAArxx84AzSgRzgXzZwU |
| 2025-02-28T10:34:09Z | user2           | created   | Another Project (#50)  | Issue added to project                                                                                            | PVTI_lADOAArxx84AzSgRzgXzZwU |
| 2025-02-28T08:19:24Z | user2           | edited    | Team - TEAMA (#37)     | Modified field "Priority": Next Month => Now                                                                      | PVTI_lADOAArxx84Avkz4zgXbG9s |
| 2025-02-26T08:24:18Z | user3           | edited    | Team - TEAMA (#37)     | Modified field "Priority": Next Week => Next Month                                                                | PVTI_lADOAArxx84Avkz4zgXbG9s |
| 2025-02-26T08:24:18Z | user3           | reordered | Team - TEAMA (#37)     | {"previous_projects_v2_item_node_id":{"from":"PVTI_lADOAArxx84Avkz4zgXbG1A","to":"PVTI_lADOAArxx84Avkz4zgW58C0"}} | PVTI_lADOAArxx84Avkz4zgXbG9s |
| 2025-02-17T17:25:31Z | user3           | edited    | Team - TEAMA (#37)     | Modified field "Priority": null => Next Week                                                                      | PVTI_lADOAArxx84Avkz4zgXbG9s |
| 2025-02-17T17:25:25Z | user3           | edited    | Team - TEAMA (#37)     | Modified field "Status": null => Todo                                                                             | PVTI_lADOAArxx84Avkz4zgXbG9s |
| 2025-02-17T17:25:22Z | user3           | created   | Team - TEAMA (#37)     | Issue added to project                                                                                            | PVTI_lADOAArxx84Avkz4zgXbG9s |
| 2025-02-17T17:05:41Z | user3           | deleted   | Project not found (#0) | Issue removed from project                                                                                        | PVTI_lADOAArxx84AxXZizgW8bCs |
|----------------------|-----------------|-----------|------------------------|-------------------------------------------------------------------------------------------------------------------|------------------------------|

But then we have to restrict access to this content since it will potentially contain data from projects with access restrictions.

It would be much better to have this available directly inside an issue timeline, whose permission for user to see these events will be driven by their access to the project.

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. ⭐