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
Related
I'm trying to setup azure devops test project and introduce it to our team. So I created test user stories and related tasks. I also created test sprints (10 work days each) starting with 2021-07-19. So far so good. Taskboard contains tasks and user stories, for test purposed I "finished" some work yesterday. Backlog tab seems to be working well, remaining work and work details works as expected too. Capacity tab is filled.
But once I enter Analytics tab with burndown trend it seems to be empty. No task nor user stories. Did I miss something? I tried all tutorials and all seems to be set correctly. See pictures below.
Do you have any advice or hints?
Thanks!
EDIT: Legacy burndown graph in dashboard works fine.
After a while I found solution. My test project contains only user stories and related tasks and thus the structure is obviously User story -> Tasks. However in the project setting -> Boards - Team configuration I left checked also Features checkbox. Based on that setting expected structure is Feature -> User stories -> Tasks which I haven't. So once I unchecked Features checkbox all started to work as expected. I might be useful for others as well.
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.
Host Details:
OS Editon: Azure Devops server 2016
OS Build: 1607
Azure DevOps Details:
AZ server: 2019
The issue:
For one Team Project, we are requiring to have three different sub-area paths so we can place work accordingly for each team Properly to follow it.
The three sub-areas were created as follow:
and visible are visible from Bords:
But, and here the issue, the Button for creating New Work Item now is Disabled, as shown below:
Also
How could re-enable this button?
We use this button at daily basis to create New Tasks or as required, is so weird that enabling one functionality we lost other.
It’s possible your workflow has the work item disabled. Check your process and see if the work item type is disabled. Also on the ribbon next to View as Board, hover and click, it will give you a more detailed error message.
If the work item is disabled you will see this message.
Solved by myself
Hello Martin, thanks for reaching me out so swiftly,
I did found the issue, due to a lack in Azure DevOps documentation didn't know that when creating a new Team Project have to create the extra teams within the Project before anything else, and then is that can proceed to add define the sub-area paths in the Boards Section and then is when is possible to have First multiple teams within a team project and Second have enabled the Work Items Button for each team sprint:
See for example this MS official documentation how they don't make any clarification of it: {{ https://learn.microsoft.com/en-us/azure/devops/organizations/settings/about-areas-iterations?view=azure-devops }} :
Also here {{ https://learn.microsoft.com/en-us/azure/devops/organizations/settings/set-area-paths?view=azure-devops&tabs=browser }} :
So MS docs miss that point completaly!
Solved each team is an independent unit and for that each will have their own setup,
Once that is corrected all works fine
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'm in the UAT phase of a project I am trying to configure my board using custom columns so I can easily track the progress of bugs through their life cycle. It seems like this is possible, but yet it doesn't quite work.
The new, active & resolved columns all show bugs - however the other columns do not, even though I have mapped them to valid statuses. I can run a query and can see there are plenty of bugs currently set to "In QA".
Why aren't they appearing in the list?
Am I going about this wrong? Is there another way to get this kind of view?
It’s mainly caused the Kanban board filter cards condition hide some work items which not meet the conditions. So in Kanban board -> click filter cards -> make sure all filter cards are not selected.
Such as If all filter cards not selected, the Kanban board will shows all user stories and bugs. If Iteration select all, there won’t show all work items.
Also please check the query conditions are correct or not as the issue said.
Create and customize in inherited processes:
In Process Tab https://account.visualstudio.com/_admin/_process, create inherited process from Agile template.
Click Bug for the inherited process, in the States Tab, add new states in Resolved category so that the bug process is: New -> Active -> Resolved -> In QA -> QA Approve -> In UAT -> Closed.
In kanban borad -> settings -> columns -> set IN QA column bug state as In QA, QA Approve column bug state as QA Approve, In UAT column bug state as In UAT -> save.