Bug work item in Agile. Removing the rule that auto assigns the work item to the persion who created it when the state is changed to resolved .
In Azure DevOps, there are many hidden state transition rules scattered across the different work item types. These rules are system generated and cannot be edited or removed. Most of them are necessary to track when a work item is activated, resolved, or closed. For a few of the rules, the value is less obvious, and in some cases are a cause of customer dissatisfaction with the product. Even though they made sense years ago, these rules have outlived their usefulness and it is time for them to be removed.
In this blog post, we wanted to share the impact of the first rule being removed. We also have a work around for those customers who still want to use the rule in their projects.
Although there are several hidden system rules across the different processes (Agile, Scrum, CMMI), the one rule that gets the most negative feedback is on the Bug work item type in the Agile process.
This rule states..
When_ the bug moves to Resolved **_then**_ automatically set the Assigned To value to the person who created the work item_
On the surface it makes sense to assign the bug back to the person who created it. They need to validate the bug is fixed. But in reality, teams don’t always work this way. Because bugs are a heavily used work item type, it makes sense to remove this hidden rule and keep things simple.
This is the first rule to be removed.
The rule will be removed from the Bug work item type in the Agile template starting in the Sprint 177 deployment (starting the week of October 19th, 2020). All projects using the system Agile process or an Inherited Agile process will be affected. Once the deployment reaches your organization, the rule will be removed from all bugs on all projects.
If you are using Hosted XML, no changes will be made to your process templates and the behavior on the bug work item type will not be affected.
For customers who like having bugs automatically assigned to the person who created them, you can create a custom rule. To do so, make sure you have created a custom inherited agile process. Then go into the Bug work item type and create a new rule. Below is a screen shot of the specific rule you can use to set the Assigned To value to Created By when the state is changed to Resolved.
In this article, I will discuss how I adapted Avi’s original canvas to the needs of the teams I was coaching, elaborate on the different elements of a working agreement, and share with you a step-by-step guide to facilitating collaborative working agreement development workshops.
What is DevOps? How are organizations transitioning to DevOps? Is it possible for organizations to shift to enterprise DevOps? Read more to find out!
DevOps and Cloud computing are joined at the hip, now that fact is well appreciated by the organizations that engaged in SaaS cloud and developed applications in the Cloud. During the COVID crisis period, most of the organizations have started using cloud computing services and implementing a cloud-first strategy to establish their remote operations. Similarly, the extended DevOps strategy will make the development process more agile with automated test cases.
The year 2020 has arrived, and its arrival brings a lot of innovations and transformations in the Information and Technology (IT) sector to DevOps technologies.
What questions should we ask when determining more about a product's dimensions? Let me show you how to facilitate a workshop based on the 7 Product Dimensions.