You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just started using devlake and have found the documentation super helpful! I did come across something in the docs for v0.21 that I'm questioning though. I've been trying to find a way to show planning accuracy which would require me to know if stories were added/removed from sprints. Looking through the database at tables like sprints, sprint_issues, and issues I wasn't finding quite what I needed so I went back to the documentation. In the Domain Layer Schema section under sprint_issues it reads:
This table shows the relation between sprints and issues that have been added to sprints. This table can be used to show metrics such as 'ratio of unplanned issues', 'completion rate of sprint issues', etc
which sounds exactly what I'm looking for but based on the columns in the sprint_issues table (sprint_id and issue_id) - I'm not seeing how it's possible to come up with those metrics.
(referencing these docs: sprint_issues).
I did find that if I go back to the docs for v0.15, I see a lot more columns in the table and I can see how you'd be able to surface the metrics with those columns.
So I'm wondering are we not able to surface these metrics in newer versions, or did the data get moved to a different table?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I just started using devlake and have found the documentation super helpful! I did come across something in the docs for
v0.21
that I'm questioning though. I've been trying to find a way to show planning accuracy which would require me to know if stories were added/removed from sprints. Looking through the database at tables likesprints
,sprint_issues
, andissues
I wasn't finding quite what I needed so I went back to the documentation. In the Domain Layer Schema section undersprint_issues
it reads:which sounds exactly what I'm looking for but based on the columns in the sprint_issues table (
sprint_id
andissue_id
) - I'm not seeing how it's possible to come up with those metrics.(referencing these docs: sprint_issues).
I did find that if I go back to the docs for v0.15, I see a lot more columns in the table and I can see how you'd be able to surface the metrics with those columns.
So I'm wondering are we not able to surface these metrics in newer versions, or did the data get moved to a different table?
Beta Was this translation helpful? Give feedback.
All reactions