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.

Sign up for GitHub

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

Jump to bottom

[Feat]: Pivotal Importer, Epics should be put into an In Progress or Done State based on Stories #81

Open
semperos opened this issue Oct 16, 2024 · 0 comments
Open

[Feat]: Pivotal Importer, Epics should be put into an In Progress or Done State based on Stories #81

semperos opened this issue Oct 16, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@semperos
Copy link
Member

The Pivotal Importer recipe already creates Epics from Pivotal Tracker epics, but it sets all of them to an Unstarted state. Using the states of constituent Stories in the given Epic would be an improvement:

  • No Stories ➡️ Unstarted Epic
  • All unstarted Stories ➡️ Unstarted Epic
  • Some (but not all) started Stories ➡️ In Progress Epic
  • All completed Stories ➡️ Completed Epic
@semperos semperos added the enhancement New feature or request label Oct 16, 2024
devin-ai-integration bot added a commit that referenced this issue Dec 10, 2024
@devin-ai-integration @mdthorpe-sc
feat: implement epic state updates based on story states
5922979 
- Add epic_states configuration to initialize.py
- Add epic_workflow_states to config in lib.py
- Add calculate_epic_state() function to determine epic states
- Update EntityCollector to update epic states after story creation

Implements #81: Epics should be put into In Progress or Done state based on Stories

Co-Authored-By: [email protected] <[email protected]>
@devin-ai-integration devin-ai-integration bot mentioned this issue Dec 10, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Milestone
No milestone
Development

No branches or pull requests
1 participant
@semperos