Project unexpectedly reverted to older version

[kylepolich]

Select Topic Area

Question

Feature Area

Issues

Body

We have been using Github Projects for years now. For the first time today, one of our Project boards seems to have reverted to one from a few weeks ago. WE don't know how this happened. There are about a dozen tickets that were formerly on the board and are now missing. Also, the order has reverted to an older version. Honestly, it seems like there was some sort of quiet database restore on the server that reverted our updates. Is there a way to restore it?

Guidelines

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

[kylepolich]

This bug was a huge setback for our small team. Devs didn't know what to work on today and our PM is out. Is a resolution coming? I'm afraid to spend a few hours rebuilding the board in case somehow that prevents a patch from fixing our Project by restoring it to the state it was in before the server side revert took place.

[marywhite]

Hi @kylepolich - sorry for the troubles. Would you mind sharing the URL of the project that's experiencing issues?

[kylepolich]

HI @marywhite Here's the URL that experienced the server side data revert: https://github.com/users/kylepolich/projects/41/views/1

[marywhite]

Thanks for the response @kylepolich. So I can troubleshoot this further, are you able to provide any of the following?

• A date where the project was last working as expected
• A URL for an issue that was previously on the project that you are no longer seeing
• Any other info on the ordering changes that you noticed - (i.e. had you previously been sorting on a particular field and the sorting is no longer applied? Are items that you had manually reordered to the top of your view no longer in their expected positions?)

[kylepolich]

Hi @marywhite I didn't have that data, but since the item occurred again, destroying our work on a different project, I was able to capture the date, url, and details. Please see my new comment below.

[kylepolich]

@marywhite this problem happened again today!

This time, a different board was ruined by the bug.

https://github.com/users/kylepolich/projects/12/views/1

The link above began the day in the correct state. I was making changes, updating our backlog, and did in-line Issue correction, for example, I created this link:

https://github.com/kylepolich/plus.dataskeptic.com/issues/2444

A few hours later, I checked back and the board no longer looks the same. It looks like it looked several weeks ago. Tickets that have previously been removed are back. Tickets that should be there are missing. The order is all wrong.

I confirmed with the other users that have access they NO ONE made any changes. They never have before, so I trust they are telling the truth.

At this point, without a fix, we will have to move off github and github projects. this is a debilitating bug that causes us dozens of man ours of time to fix. If you can't fix the bug, you should at least provide a mechanism for us to export a backup of this so that I can get my assistant to rebuild it every time this happens in the future. Currently, we have just lost all our work.

Can you please confirm the issue and advise on when we might see a fix?

[marywhite]

Hi @kylepolich. Sorry that you're running into difficulties again. Looking at the audit history for this project, I am seeing events that include reordering from yesterday attributed to another collaborator on the plus.dataskeptic.com repository. Are you aware of any subsequent changes to the project that might have occurred after you noticed the unexpected state?

I see https://github.com/kylepolich/plus.dataskeptic.com/issues/2444 was recently created and still exists in the project. If you have a link to an issue that was previously removed, or one that returned it would be helpful to debug further.

[kylepolich]

Hi @marywhite , yes as this is our companies way of organizing work, we had no choice but to try and repair the board as best we could. We really need this fixed or a backup option so that we don't have to guess when we reorder. Now, we've taken to hiring a new person to take daily screenshots as a defense agains this debilitating bug.

[kylepolich]

@marywhite We experienced the bug again today! It is totally debilitating for our team. At this point, we have to find another solution. Thanks anyway for looking, but we need a more professionally, tested project management solution.

[kylepolich]

The most recent (now the 3rd time this bug has occurred) was on https://github.com/users/kylepolich/projects/12/views/1

That's the same board as last time. At this point, we're abandoning Github Projects due to instability.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[kylepolich]

I think it was inappropriate to close this when no solution was ever deployed. If you don't care about users, I guess it's fine to just leave this critical bug out there.