How do I add a state to a Bug with Value = Reopened.
We have only New, Active, Resolved and Closed configured in the bug status dropdown.
The New, Active, Resolved and closed states are the Default State for the Bug Work item.
From you screenshot, you are using the Default Agile Process. The default agile process cannot be changed. So you need to create an inherited Agile process. Then you could modify the inherited process.
Here are the steps:
Step1: Create an inherited Agile process in Organization Settings -> Process.
Step2: Add the Reopend state to Bug Work item in New Inherited Agile process -> Bug -> States -> New state.
In order for your project to use this new inheritance process, you need to change the project process in Organization Settings -> Process -> Agile(Default) -> Projects ->Change Process.
Create an inherited process if you do not have one already (i.e if you are using one of the built in processes), and change process used by your project to use the new one
Add a custom state to your process
The type of states available seem to be defined by the project settings.
According to Microsoft Azure DevOps Documentation it seems like the state categories you mention come from setting the project as Agile Process.
The same documentation page also lets us know that you can add custom states. Presumably if you have the correct permissions to do so.
Also, please consider updating your title to something like "How to set bug to state 'Responded' in Azure Devops?", or something similar, descriptive.
Related
We rolled ADS out as our main development platform a few months ago and generally have be working pretty well in it. However, one of the things I've noticed is I (project admin) am unable to set Epics or Features to a state outside of "New", "Close", or "Removed". The feature I added a picture of has 2 child user stories - one of which is "Active" and one which is "Resolved". It also has a parent Epic which is set to "new" because I'm unable to change the state of that one to Active either. As far as I can tell, I've added all the information I can to the feature, and based on the Microsoft documentation it appears I should have more states available but can't figure out what I'm missing.
Any help would be appreciated!
1 - Are you sure that you have defined state which you want to use in your Process definition?
Process name that you currently use in your project can be found here https://dev.azure.com/MyOrganizationName/ProjectName/_settings/
Process states definition can be found here https://dev.azure.com/MyOrganizationName -> Organization Settings -> Boards -> Process -> -> <Select 'Feature' work item> -> States
2 - Maybe someone has restricted state transition creating new rule for your process? Like in this example?
Documentation regarding this can be found here
https://learn.microsoft.com/en-us/azure/devops/organizations/settings/work/apply-rules-to-workflow-states?view=azure-devops#restrict-state-transitions
If I create a new project and select the Agile process, my user stories will be grouped in iterations Eg "MyProject/Iteration 1".
However, If I create the project using Basic process and after the project has been created, changes the process to Agile I can group my user stories by Sprint Eg "MyProject/Sprint 1".
The latter is what I want, however as the process was set to Agile when the project was created (not by me), I'm trying to figure out how to change it to use Sprints as default?
Side note:
I cannot create a new project as I lack privileges
I cannot create a new process as I lack privileges
I cannot change to another process because I've already created a bunch or user stories
Although I can create sprints manually, I want it to be default.
Thank you!
From this document, we can know that iteration and sprints represent the same concept in the agile process.
Define Iteration Paths (aka sprints) and configure team iterations
So if you want to visually use Spirits as the default, you can add a new iteration named Spirit in team configuration, or change the name of the existing iteration to the Spirit style. Then set it as Default iteration. As shown in the following figure:
Because your current project is already Aglie process, the initial display must be MyProject/Iteration 1. If you want to display like MyProject/Sprint 1, you have to modify it later.
There are two ways to change the display: changing the process or manually modifying it.According to your Side note, obviously neither is feasible.
If you really want Spirits as default in agile progress project without any manual modification,you could submit a feature request in our Develop Community site. Our PM and product team will kindly review your suggestion.
There is no way to do this without changing the Process of your project.
My team is currently using the CMMI board in Team Services and we would like to switch to the Agile board. I was told we can't just change the template, but I can't figure out how to export all of our open tickets to a new board. How do I easily change our team's board. Thanks!
At the moment this is technically not possible. When you choose a Process, during project creation, you can't change it to a new parent later. So you pick CMMI, or Agile or Scrum and later you can only change to a derived template.
What you can do though, is create an inherited process template and customize it until it looks and feels the same as another process template. It's quite a bit of work, but doable.
It is expected that changing from one base template to another will be added somewhere in the future. But at the moment it's not showing up on the TFS/VSTS feature timeline.
There is no easy import/export option either, though there are a few tools, like VSTS Sync Migration Tool that can copy over work items and map them to a new structure. I'll probably just be as much work as creating an inhertited process though.
Is it possible to customise the transitions between states on work items on VSTS? I have some custom states and want to restrict what the next available states are.
For example when a new bug is raised in the 'New' state the user should only able to select 'In Progress', 'Rejected' etc. But they should not be able to selected 'Closed'
This was possible in TFS but I can't find anywhere in VSTS to do this.
Currently it's not possible to add restrictions to the state workflow using work item rules. Though there may be a couple of tricks by clearing a field, making it read-only and making it required when the state is changed to an undesirable state.
Work Item rules were a recent addition and not all restrictions from the old XML model are currently supported.
When you import a TFS collection into VSTS there is an option to keep using the XML model to manage processes. Those accounts do support many of the old configuration options and restrictions.
I have an issue in JIRA that is following one workflow, workflow looks something like this (for bugs):
New -> Eval -> Approve -> Roadmap/Schedule -> Dev -> Complete
This workflow is for issue type "Bug".
For higher priority bugs, I want a totally different workflow, and for it to have its own issue type, for instance "Priority Bug".
R&D -> Dev -> Release -> Complete
This works great, for new Priority Bugs, but I have a transition, that allows you to promote a normal bug to a priority bug. That transition changes the issue type to Priority Bug properly, but when it gets there, it seems lost, its now not in either workflow. How do I get it to change workflows as well?
I suggest to install Script Runner plugin, and implement this as a single workflow. You can have custom scripted conditions that will check the type of the issue and allow and disallow your transitions thus emulating like it is a different workflow for another issue type.
Workflows are for a given project and for a given issue type. If the bug is in a particular project and of a particular issue type then it will follow the corresponding workflow.
However, when moving from one workflow to another there needs to be some way for JIRA to know what state to go to. When you do a manual move you get a prompt that allows you to decide what state in the new workflow it has. I have never done an automatic move triggered by a transition, but I suspect it will have a problem determining what state the issue should have. Perhaps you could set the state as a part of the transition?