4 ms·
The code is the work. The pull request is the workface. Add automation to comment on stories that "a branch was pushed," or "a pull request was created." Then y
by turtleyacht 2y ago
The code is the work. The pull request is the workface. Add automation to comment on stories that "a branch was pushed," or "a pull request was created." Then you know someone is waiting to review or it's still in progress.
A Jira query is easy enough to set up for "stories that have changed status in the past day." Check daily.
If stories aren't moving, maybe team is collaborating around current issues. That's for certain if a new deployment hasn't made it into staging.
- propernun 2y agoAgreed we should look into automating the workflow. I think Jira has something where it can track git commits
- turtleyacht 2y agoAnother idea is adding a swimlane for Acceptance or Delivery. Even after a code change is merged, QA-certified, and deployed, stories can go here for release notes, training docs, or final intake. Not sure if it works over a longer period, but that was one of the workarounds for too many Done stories to catch up on from a post-sprint perspective.
- turtleyacht 2y agoBy commit might be too fine-grained, but Jira Automation (no-code) has a Trigger or Condition for "pull request merged" or something similar.
- propernun 2y agoYes I meant PR. Thanks for the suggestions.