Hey community 👋The title is maybe not the best but I wasn't sure how to frame it. So here's the situation:
One developer is doing true CI, meaning small batch sizes and multiple PRs per sub-task. This leads to the situation that we have a story with sub-tasks which's sub-tasks in turn have multiple PRs.
How to deal with that now when it comes to the design of the Kanban system? We have a column 'Code Review' which is displaying the work status for items in CR. But now we have a sub-task which is in 'Code Review' but actually is moving between 'In Progress' and in 'Code Review' all the time (because of the multiple PRs.
So how do you resolve the issue of the individual process (which is good software craftsmanship here IMO) vs the design the tool (JIRA) allows (or let's say restricts) here?
The benefit of the Kanban design which could potentially surface bottlenecks in code review vs what the tool allows is tricky.
Same applies for workflow automations. The rule commit > in progress/PR open > in code review does not work here.
Any experience on that topic?
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events