-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Tooling] Obtain and track estimates for milestones #8359
Labels
4 - verified
Issues that have been released and confirmed resolved.
estimate - 3
A day or two of work, likely requires updates to tests.
p - medium
Issue is non core or affecting less that 60% of people using the library
tooling
Issues relating to build system fixes or improvements.
Milestone
Comments
benelan
added a commit
that referenced
this issue
Oct 1, 2024
**Related Issue:** #8359 ## Summary Add an action that creates a spreadsheet and JSON file with the total estimates per milestone. The action runs when an issue closes and can be manually dispatched. The files are saved as artifacts in the workflow run. I'll add a wiki page about running the workflow and retrieving the data once it's live. It might be because I'm a GraphQL noob, but Monday's API reference was not very helpful. I can give the integration another try if this is not ergonomic enough.
Installed and assigned for verification. |
For verification, please follow the usage instructions on the action's wiki page: |
🍠✨👌 Verified with both the CLI and Web instructions provided on the wiki above 👆 |
benelan
added a commit
that referenced
this issue
Feb 8, 2025
**Related Issue:** #8359 ## Summary Add an action that creates a spreadsheet and JSON file with the total estimates per milestone. The action runs when an issue closes and can be manually dispatched. The files are saved as artifacts in the workflow run. I'll add a wiki page about running the workflow and retrieving the data once it's live. It might be because I'm a GraphQL noob, but Monday's API reference was not very helpful. I can give the integration another try if this is not ergonomic enough.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
4 - verified
Issues that have been released and confirmed resolved.
estimate - 3
A day or two of work, likely requires updates to tests.
p - medium
Issue is non core or affecting less that 60% of people using the library
tooling
Issues relating to build system fixes or improvements.
Summary
Refer to the "Estimate tracking strategery" chat for the Monday API token, if needed.
cc: @brittneytewks
Desired Outcome
Resources
As far as past milestone tracking, it looks like we started getting the majority of issues estimates in May, so if possible if we could get total estimates for the closed milestones listed below:
Milestone links:
The text was updated successfully, but these errors were encountered: