2 ms·
This really feels like a workflow issue where you have to discuss with your team how to best categorize the work. I've seen below categories with state transiti
by aprdm 6y ago
This really feels like a workflow issue where you have to discuss with your team how to best categorize the work. I've seen below categories with state transitions work well..
* TODO
* In progress
* On hold
* Awaiting feedback
* Pending Release
* Done
- lbriner 6y agoThis sounds correct but I cannot find articles that talk about how these are automated in real life to avoid someone having to manually watch for the various deployment stages and update tasks or PBIs manually. It seems like something that everyone would try and automate in a devops organisation so I am not sure how to search for e.g. "Tracking and automating task updates in Devops". Maybe it is simply a question of basic webhooks but most tools seem to track commits rather than tasks so it might be quite messy trying to reverse engineer the task numbers for each commit so that the CI/CD tool can update the task.
- aprdm 6y agoI never bothered to automate anywhere I worked... it is a <1 min task done once a day, which is usually more useful if it comes with a higher level human description. The automations I've had is to link jira to gitlab or perforce based on regex from the comments so that people can easily click around code and discussion.