Timestamp fields in GitHub Projects

[sunnyi101]

GitHub Projects now includes three built-in timestamp fields: Created, Updated, and Closed. You can add them to any project view to sort and filter work based on when it was opened, last updated, or closed.

Area.mp4

• Created: When the issue, draft issue, or pull request was created.
• Updated: When the item was last updated, including both issue/pull request changes and project field changes like updating the status. This timestamp can differ between projects for the same item.
• Closed: When the issue or pull request was closed, making "recently completed" views easy to build.

To get started, click + to add a field in any project and select Created, Updated, or Closed from the list.

Share your feedback!

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

[bewuethr]

I'm not sure if I overlooked it, but I've been unable to see these new fields as date fields in the roadmap view. Are they there?

[sunnyi101]

We are currently not supporting the new fields in the roadmap view

[ken-mellem]

Is there a plan on supporting these timestamp field in the Roadmap view?

[sunnyi101]

We are currently not supporting the new fields in the roadmap view

[christianpatrick]

This is amazing! It’s exactly what I needed to remove the need for custom dates. Can we group by these fields with the Table view in the future?

[dennison33]

Are they date fields or date time (timestamp) fields? I see the created field looks like a date, no time.

[computersalat]

What about missing timestamps on downloading files ?
e.g.

>wget -m -nH --cut-dirs=5 'https://github.com/gradle/gradle/archive/refs/tags/v7.6.6.tar.gz'
--2026-06-21 11:45:05--  https://github.com/gradle/gradle/archive/refs/tags/v7.6.6.tar.gz
Auflösen des Hostnamens github.com (github.com)… 140.82.121.4
Verbindungsaufbau zu github.com (github.com)|140.82.121.4|:443 … verbunden.
HTTP-Anforderung gesendet, auf Antwort wird gewartet … 302 Found
Platz: https://codeload.github.com/gradle/gradle/tar.gz/refs/tags/v7.6.6 [folgend]
--2026-06-21 11:45:05--  https://codeload.github.com/gradle/gradle/tar.gz/refs/tags/v7.6.6
Auflösen des Hostnamens codeload.github.com (codeload.github.com)… 140.82.121.9
Verbindungsaufbau zu codeload.github.com (codeload.github.com)|140.82.121.9|:443 … verbunden.
HTTP-Anforderung gesendet, auf Antwort wird gewartet … 200 OK
Länge: nicht spezifiziert [application/x-gzip]
»Last-modified«-Kopfzeile fehlt -- Zeitstempel abgeschaltet.
--2026-06-21 11:45:05--  https://codeload.github.com/gradle/gradle/tar.gz/refs/tags/v7.6.6
Wiederverwendung der bestehenden Verbindung zu codeload.github.com:443.
HTTP-Anforderung gesendet, auf Antwort wird gewartet … 200 OK
Länge: nicht spezifiziert [application/x-gzip]
Wird in »gradle-7.6.6.tar.gz« gespeichert.

gradle-7.6.6.tar.gz                       [              <=>                                                       ]  25,13M  9,11MB/s    in 2,8s    

2026-06-21 11:45:08 (9,11 MB/s) - »gradle-7.6.6.tar.gz« gespeichert [26347633]

BEENDET --2026-06-21 11:45:08--
Verstrichene Zeit: 3,3s
Geholt: 1 Dateien, 25M in 2,8s (9,11 MB/s)

the important part is:

»Last-modified«-Kopfzeile fehlt -- Zeitstempel abgeschaltet.

is it globally switched off ?
And if so why ?

[OffCrazyFreak]

Two more surfaces where these fields don't resolve, in addition to the roadmap view already raised above.

1. The item detail side panel shows None yet

Opening an item from a board view lists Created and Updated in the field sidebar, but both render None yet, while the header of that same panel correctly says "opened last month" for the item. None yet is the same placeholder used for genuinely unset custom fields, so it reads as missing data rather than "not available on this surface".

The same items show the correct values in a table layout view, so it's specific to the side panel.

2. The GraphQL API returns no value for them

Querying ProjectV2Item.fieldValues returns entries for every other field on an item (Status, Priority, Size, custom single-selects) but nothing at all for the CREATED / UPDATED / CLOSED fields.

The fields themselves are returned by ProjectV2.fields with dataTypes CREATED, UPDATED and CLOSED, so they are discoverable but not readable per item. That makes them unusable from scripts and automation for now.

content.createdAt / content.updatedAt works as a partial workaround, but it doesn't match the documented semantics of the Updated field, which is supposed to also reflect project field changes such as moving Status.

A smaller related observation on Updated: for a draft issue whose body I edited (the UI shows "yesterday (edited)" on the body), DraftIssue.updatedAt still reports the original creation timestamp, about four weeks earlier. I can't tell whether the Updated field itself tracks that, since it isn't readable via the API.

Is there a plan to surface these in the side panel and in the API?