Skip to content
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

Closed
geospatialem opened this issue Dec 6, 2023 · 3 comments
Closed

[Tooling] Obtain and track estimates for milestones #8359

geospatialem opened this issue Dec 6, 2023 · 3 comments
Assignees
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.

Comments

@geospatialem
Copy link
Member

Summary

  1. Create tooling that provides us with historical time estimates on closed milestones and
  2. Initiate automation that provides us with time estimates via Monday once a milestone is closed

Refer to the "Estimate tracking strategery" chat for the Monday API token, if needed.

cc: @brittneytewks

Desired Outcome

  • Get a historical perspective on time estimates with milestones since May 2023
  • Continue to get additional insights and stats on estimates with upcoming milestones as they close

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:

  • List of milestone numbers, if its more useful: 110,129,132,121,122,134,135,136,123,138,124,144,145,126,127,128

Milestone links:

@geospatialem geospatialem added tooling Issues relating to build system fixes or improvements. 1 - assigned Issues that are assigned to a sprint and a team member. p - medium Issue is non core or affecting less that 60% of people using the library estimate - 3 A day or two of work, likely requires updates to tests. labels Dec 6, 2023
@geospatialem geospatialem added 2 - in development Issues that are actively being worked on. and removed 1 - assigned Issues that are assigned to a sprint and a team member. labels Sep 23, 2024
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.
@benelan benelan added 3 - installed Issues that have been merged to master branch and are ready for final confirmation. and removed 2 - in development Issues that are actively being worked on. labels Oct 1, 2024
Copy link
Contributor

github-actions bot commented Oct 1, 2024

Installed and assigned for verification.

@github-actions github-actions bot assigned geospatialem and DitwanP and unassigned benelan Oct 1, 2024
@benelan
Copy link
Member

benelan commented Oct 2, 2024

For verification, please follow the usage instructions on the action's wiki page:
https://github.com/Esri/calcite-design-system/wiki/milestone-estimate-tracking

@DitwanP
Copy link
Contributor

DitwanP commented Oct 3, 2024

🍠✨👌 Verified with both the CLI and Web instructions provided on the wiki above 👆

@DitwanP DitwanP closed this as completed Oct 3, 2024
@DitwanP DitwanP removed the 3 - installed Issues that have been merged to master branch and are ready for final confirmation. label Oct 3, 2024
@DitwanP DitwanP added the 4 - verified Issues that have been released and confirmed resolved. label Oct 3, 2024
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.
Projects
None yet
Development

No branches or pull requests

3 participants