GitHub Community
[Projects Beta] issue history not updated when moved issue between columns or change status (Board) #5859
-
|
Hi. I'm excited to try a new Beta version, we already moved some of our projects to Beta. One issue I found is related to history. Adding screenshot. Please let me know if you need more details. EDITED: there is no history about who and when added issues to project |
Beta Was this translation helpful? Give feedback.
Replies: 16 comments 36 replies
-
|
this issue bothers me as well |
Beta Was this translation helpful? Give feedback.
-
|
Upvoted this one too! Seeing the history of when an issue changed from previous statuses is highly valuable. I need to see who/when changed the status. I have no idea who to ask if I don't know why an issue is in a certain status. This is available in the current 'Projects' just not in the Beta. |
Beta Was this translation helpful? Give feedback.
-
|
Totally agree. |
Beta Was this translation helpful? Give feedback.
-
|
Wondering if this is task 3 from github/roadmap#287 ?
|
Beta Was this translation helpful? Give feedback.
-
|
@timoyates @ankneis will someone be keeping us up to date while @azenMatt is on leave for the next several months? Seems like this one is due here in Q4 2022 but still not showing on the roadmap as @azenMatt has suggested recently. |
Beta Was this translation helpful? Give feedback.
-
|
@tpak There is an internal roadmap issue that is currently being reviewed. It has not yet been published because we are publishing new issues from the internal roadmap to the public roadmap on October 19. |
Beta Was this translation helpful? Give feedback.
-
|
@ankneis, thank you for the reply and shedding a little light on your process, unfortunately, you are linking to the internal or private repo, so again, we get a 404 I guess we will have to wait until 19-October and hope that we get an update. As I said here: https://github.com/orgs/community/discussions/5859#discussioncomment-3665175 communications on this is key and this functionality is all about communications. |
Beta Was this translation helpful? Give feedback.
-
|
@tpak Sorry for the confusion and linking to a repo that you cannot access. Summary here is to look out for the published and updated issue on October 19. |
Beta Was this translation helpful? Give feedback.
-
|
Hello people, it's November 21 already, and I don't see this feature in my issues yet. Any update about this demand? |
Beta Was this translation helpful? Give feedback.
-
|
This is a pretty serious issue and I question the logic behind the priorities of their roadmap. Why would a task like adding 'Themes' to github projects beta be before a task like this? They need to really double check which features are nice-to-have and which features, like this one, affect the core functionality of any project management tool. Giving Github Projects Beta the core functionality that already exists in Github Projects should be priority 1. |
Beta Was this translation helpful? Give feedback.
-
|
@ankneis thanks for the reply 🙏 -- I guess since you removed it I was hoping you
could shed light on why/when we will see parity with classic projects. Also
the link you provided 404’s
This item provides critical communication and info about the journey an
issue takes within a project or projects. Who moved an issue around and
when often provides a critical bit of info to devs and other actors. I
find it odd that classic projects is now deprecated and such glaring
functionality left out of the new product.
@timoyates? @azenMatt is there any update or info you can provide?
(although, based on @azenMatt not commenting or updating other issues such
as issue templates in 3 months it’s not clear he is still around?)
Communication is key, this issue is all about communication. Both in the
real and meta sense :-)
…On Fri, Sep 16, 2022 at 9:58 AM Allison Kneis ***@***.***> wrote:
👋 - Looks like this comment
<https://github.com/github/roadmap-internal/issues/503#issuecomment-1092876610>
mentioned "Project events in issue/pr timelines" was a "ways out". I'd
follow up with @timoyates <https://github.com/timoyates> and @azenMatt
<https://github.com/azenMatt> to get a more concrete timeline since it is
also not listed on the Milestone 2 Issue
<https://github.com/github/roadmap-internal/issues/665>.
|
Beta Was this translation helpful? Give feedback.
-
|
replied in the thread here 😄 |
Beta Was this translation helpful? Give feedback.
-
|
@timoyates @ankneis can someone please give us an update on this? It has not appeared as suggested as item on the roadmap - @azenMatt has teased that this critical functionality was pending and would be available shortly before he went on extended leave and when @ankneis had removed it from the parity issue as a bullet point github/roadmap#483 We will not move our projects until we can see the activity in the issues; even in my tiny organization, it is information we rely on. |
Beta Was this translation helpful? Give feedback.
-
|
@tpak Thanks for the ping! We are still working on this feature. It was removed from the referenced issue as planned but we missed the cut on adding it to another. It will re-appear in the next roadmap update! |
Beta Was this translation helpful? Give feedback.
-
|
@timoyates can you provide any guidance on "when" we will see it - this is a pretty basic requirement from our POV - to be able to see who/what/when issues are added/moved/removed from a project and into what status/column and by whom - very surprising it is not a priority to get this essential functionality in a project management tool |
Beta Was this translation helpful? Give feedback.
-
|
Please understand, it is very frustrating to get dribbles of information - we'd like to move over to new project but this is absolutely a requirement and a blocker for us |
Beta Was this translation helpful? Give feedback.
-
|
+1 for @tpak. It really seems an easy feature to be added IMO, I don't understand why it's taking too long. Can you provide some deadline for this feature to be added? |
Beta Was this translation helpful? Give feedback.
-
|
Hi folks, this feature was re-added to the roadmap two weeks ago. The issue to subscribe to is the following: github/roadmap#613 Rest assured - development is active and you will be the first to know when it is rolled out or we kick off early access. |
Beta Was this translation helpful? Give feedback.
-
|
+1, this feature would be very useful! |
Beta Was this translation helpful? Give feedback.
-
|
I need someway to track who changes the status of an issue. Even if this doesn't show up on the history of the issue itself (which it should), there should atleast be a log in the project somewhere of all status changes, who they were done by and when they happened.. |
Beta Was this translation helpful? Give feedback.
-
|
Eu concordo |
Beta Was this translation helpful? Give feedback.
-
|
Hi everyone - we just released an update that now includes this history! https://github.blog/changelog/2023-01-12-github-issues-january-12th-update/ This means there are events for:
This works for both issues and Pull Requests. We ran all the existing events into the system for this so all events you've previously performed are included as well as any new events. Please give it a try and let me know if you have any thoughts / questions 😄 |
Beta Was this translation helpful? Give feedback.
-
No ETA but we are currently reviewing the next steps for our improved |
Beta Was this translation helpful? Give feedback.
-
|
Welcome back @azenMatt, and thank you, this is great news! |
Beta Was this translation helpful? Give feedback.
-
|
This is great! As with any new feature I'm sure folks have a follow-on - are there plans to reflex custom field changes in the history? If I make a weight field for a project it can change without any history recorded. Happy to follow an issue / discussion for this as well. Thanks @azenMatt |
Beta Was this translation helpful? Give feedback.
-
|
Hey @tayloramurphy - our thinking was that this might make the timeline in the issue/pr a bit too messy. However - this information is certainly needed. Ideally this would come in an 'activity history' style page inside the project. We do have this tracked in our public roadmap here - https://github.com/orgs/github/projects/4247/views/7?pane=issue&itemId=14542755 - although I think that date is a bit optimistic. I'l talk to the team and get it updated if it is. |
Beta Was this translation helpful? Give feedback.
-
|
@azenMatt really appreciate the response and the link! Agreed that it would be noisy - a way that GitLab solved this was to have a toggle on the issue page to view comments, activity, or both. That would help a bit. https://docs.gitlab.com/ee/user/discussions/#show-only-comments I should mention too - I actually already have this b/c of the Refined GitHub extension
|
Beta Was this translation helpful? Give feedback.
-
|
Hi, @azenMatt and @ankneis. Thanks for delivering this! I have been so swamped that I have had little to no time to give this a proper test, but I like what I see so far! I just wanted to drop in and provide a (very) little feedback, say thanks, and let you know you and your teams are appreciated! 🙏 |
Beta Was this translation helpful? Give feedback.
-
|
I see history of field changes when these fields are Single Select (like status) field, but do not see changes of other field types (mostly Iteration, but also Number). |
Beta Was this translation helpful? Give feedback.
-
|
Oh thanks. @azenMatt says there it's begin tracked but the link he added shows the issue is completed, though. |
Beta Was this translation helpful? Give feedback.
-
|
it looks like it was moved out of that release. We are currently working with the team to the issues tab in that project updated which should give more clarity cc @2percentsilk |
Beta Was this translation helpful? Give feedback.
-
|
@azenMatt got it, still waiting for some clarity on this, thanks. It's what's blocking me from adding editing permissions to the PMs in my org, I need visibility as to who changed what. |
Beta Was this translation helpful? Give feedback.
-
|
I also don't see when the Priority field changes which is a single select just like the Status field? |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately, I cannot find any clarifying information on this point. @azenMatt Are there still plans to provide a history in the issues timeline for fields other than the status? I would love to see this feature. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for porting this feature from classic Projects! Has this feature been rolled out to all users? We recently migrated our classic board to the beta, but PRs in our organization's repositories still do not show status changes in their timeline. |
Beta Was this translation helpful? Give feedback.
-
|
Hi everyone, |
Beta Was this translation helpful? Give feedback.
-
|
@MarioGith if this is still important for you I would suggest upvoting https://github.com/orgs/community/discussions/49602 which is currently the highest ranked API and Webhooks discussion that is related to this missing feature of the GraphQL API. @jesuslinares has also summarised the other related discussion in their comment. |
Beta Was this translation helpful? Give feedback.
-
|
Made JS scrapper for this problem https://github.com/vadimfrolov/Github-Issue-parser-JS |
Beta Was this translation helpful? Give feedback.
-
|
This is still very much needed fix to the GraphQL API. What's the point of supporting this data on legacy projects but not with the new ones? Please provide us issue history including the information of when an issue moved between columns or changed status. |
Beta Was this translation helpful? Give feedback.
-
|
This is not resolved on GHES! |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Hi @Ygilany - acknowledged this is still a gap on the GHES side. There is a small chance it may make 3.16, but 3.17 is much more likely. |
Beta Was this translation helpful? Give feedback.
and others
Hi everyone - we just released an update that now includes this history! https://github.blog/changelog/2023-01-12-github-issues-january-12th-update/
This means there are events for:
This works for both issues and Pull Requests.
We ran all the existing events into the system for this so all events you've previously performed are included as well as any new events.
Please give it a try and let me know if you have any thoughts / questions 😄