Need automatic change log (history) for custom field changes or ability to trigger a workflow when they change #86690
Replies: 11 comments
-
Please, we need change log (history) for any custom field! |
Beta Was this translation helpful? Give feedback.
-
🕒 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 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 Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
This is still important for us, is there any update? |
Beta Was this translation helpful? Give feedback.
-
Using custom fields for estimation, but not having visibility into when the value was changed, is a bit of a pain. Ideally, all fields would trigger updates, similar to a status or label change today. |
Beta Was this translation helpful? Give feedback.
-
Any update? Can we know at least if you're tracking those changes but not displaying them on the UI? Is there any workaround? I've try to use GraphQL but I wasn't able to find a query that retrieve the information I need. No having this traceability is a blocker for us. |
Beta Was this translation helpful? Give feedback.
-
🕒 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 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 Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
We still need this please do not close it or mark it dormant |
Beta Was this translation helpful? Give feedback.
-
I cannot agree more, that this is crucial for Project Planning. Serriously one of the reasons I consider going away from GH projects.. Impossible to track who changed what and when makes it nearly unmanagable |
Beta Was this translation helpful? Give feedback.
-
🕒 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 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 Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
The feature is still needed. The best workaround so far while using GitHub projects is taking periodic snapshots - not ideal at all. |
Beta Was this translation helpful? Give feedback.
-
🕒 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 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 Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Feature Area
Issues
Body
If a user adds or removes a label from an issue in a Github project, a change track post is added to the issue like this: " added the label on ".
Github custom fields are more powerful than labels because they can be better sorted, filtered and edited in the table view. And they can be use to create columns in the table view.
However to use them for important processes/information we need to have a history of the item recorded in a similar way to when labels on an issue are changed.
We could build this ourselves but unclear from https://github.com/orgs/community/discussions/68798 if it is possible to trigger a workflow when a custom field is changed
Guidelines
Beta Was this translation helpful? Give feedback.
All reactions