4 ms·
I read this over a few times and am having trouble understanding the workflow you are trying to achieve. PBIs are Pending Backlog Items? I think where you are
by jtchang 6y ago
I read this over a few times and am having trouble understanding the workflow you are trying to achieve. PBIs are Pending Backlog Items?
I think where you are going wrong is that you are saying Tasks or Backlog Items should map to CI/CD statuses. This is not always the case. Depending on the actual task (or feature) you may not always have a status in your CI/CD pipeline.
The "Done" state of a task is something I've had conversations about in many organizations as they try to mature their processes. In many cases it needs to be broke out more (waiting for QA / done but waiting for internal verification / etc).
- lbriner 6y agoSorry for the confusion. I guess the simple question is do I either a) Set as task to Done as soon as the code is merged or b) Only set it to done after it is deployed to production. If b) how can I map CI/CD tooling back to tasks so that they can track and update these tasks. PBI = Product Backlog Item as distinct from a Bug. 1 PBI = 1 or more tasks.