Sunsetting Projects (classic) breaks existing functionality

[slinna]

Select Topic Area

Bug

Feature Area

Projects

Body

Now that GitHub is sunsetting the legacy Projects (https://github.blog/changelog/2024-05-23-sunset-notice-projects-classic/), I would like to point out that this move will break existing functionality that we have implemented for several of our customers. The problem is that there is no API-level feature parity, as the ProjectsV2 lacks the issue history as pointed out in these forum discussions:

https://github.com/orgs/community/discussions/39668
https://github.com/orgs/community/discussions/5859

We are using GraphQL as per your recommendation at the time we started working with your API. But it's still not providing the essential functionality for ProjectsV2 that our customers have been using for years with the Projects (classic).

Is it too much to ask you to implement the issue history for the new Projects before the forced migration on August 23?

Guidelines

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

[slinna]

@evi-liu, that's great news, I'm looking forward to hearing more updates!

[slinna]

@evi-liu, is there any ETA for when the GraphQL API support for the issue history will be available? The forced projects v2 migration is now one month away, and we'd need some time to implement the changes before our customers' existing functionality breaks.

[evi-liu]

Hi @slinna, I just checked, and while we were very close to releasing this, we unfortunately encountered a couple of blockers at the end. I’ll work to get it prioritized as soon as possible, though it’s unlikely to be ready this month. Apologies for the missed ETA.

[slinna]

@evi-liu do you have a new ETA to share?

[jrousseau-gie-iris]

Do you have any news regarding the fix date?

[rileybroughten]

You'll now see additional events in GraphQL including Status changes on an issue. Check out the changelog for more details!

[slinna]

@rileybroughten that's great news, we'll give it a try!

[Xelliese]

If immediate resolution isn’t feasible, consider creating a custom solution that uses GitHub’s API to replicate the issue history functionality. For example, you can use the GitHub GraphQL API to query and aggregate issue data from the classic projects into a separate database or system.