Zenhub/github Data refresh

lzim / teampsd

Team PSD is using GitHub, R and RMarkdown as part of our free and open science workflow.

GNU General Public License v3.0

9 stars 23 forks source link

Zenhub/github Data refresh #2847

Open ghost opened 1 year ago

ghost commented 1 year ago

@epearman to complete the following:

[ ] Label the Epics from github zenhub data - create pull request for this - can decide later if we should keep them or not as missing data.
- [ ] use some of the code you created with this commit
[ ] Decide what labels fall under which value streams data with missing value streams.
- [ ] use some of the code you created with this commit
[ ] refresh data and provide to Libby

lzim commented 1 year ago

@epearman

I am not understanding the why/how for removing Epics from GitHub/ZenHub Data. Was this discussed at a workflow meeting? Who was there?

Please provide the rationale and context for this activity. Thanks!

FYI: @emilymetcalf114

Remove Epics from github zenhub data - create pull request for this Use some of the code you created with this commit Decide what labels fall under which value streams data with missing value streams. Use some of the code you created with this commit refresh data and provide to Libby

ghost commented 1 year ago

@lzim

David N and I discussed this asynchronously on #crossref lzim/research#469. Because EPIC cards are just a summary card of all the cards for that EPIC and do not have assignees or estimates. We thought it would be best to remove them from analysis. However, we can discuss this at next weeks team_time before making it a final decision. There are n=42 EPIC cards.