I am very new in DevOps, and I need to add a parent to parentless tasks in DevOps. I used a third-party tool to upload the user stories and tasks, and I think this is were it went wrong. When I click on a user story, I can see the tasks linked as children - but my coworkers keeps getting them on their boards as parentless. Any good fixes for this?
Looked online, didnt find any suitable solution.
You likely have Teams set up in ADO, and your coworkers aren't part of the team the parent story is set to (its iteration path). I would check with Team(s) your coworkers are members of, and check which iterations they are able to see on their backlog & boards.
You can easily bulk-update the iteration path on the tasks and stories from a query, or from the backlog view under which they are set.
Related
Is there some kind of an app/widget which helps you track your work items? We have an issue when working on multiple projects, people keep forgetting to set work items as active and DevOps doesn't calculate hours spent on work correctly
Would be useful to see which of my work items are active or paused in one list
Yes, there is a method.
State paused for example.
First, set up a query and save it.
Second, go to the Dashboards of Overview.
After that, just share the Dashboards page to others and everybody of your team can easily know how many work items are in 'paused' state and everyone can easily click in to check what are the work items are in 'paused' state(Do not forget to click 'Done editing' at the end).
By this method, you can manage other states of workitems.
I am setting up a process in azure devops based off the agile process
When I create a story (or feature etc) in the "backlog" section, it shows up on my kanban board. I want to keep my stories that aren't ready to begin being worked on somewhere else so i dont have a huge list of stories on my board.
Any idea about how to do this?
For clarification...I've added an item to the backlog but not yet assigned it to a sprint:
And here is the kanban board.
Since I haven't assigned the story to an iteration yet, i don't want it to show on the board...
Is this doable?
It sounds like you've not set up any iterations yet. By default, you'll have 1 iteration. Go to https://yoururl/_settings/work and create some child iterations.
Anything which is on the backlog would have the base iteration path, with items in an active/future sprint/iteration having a child iteration path set.
Since the process of one A/B test usually takes multiple sprints I would like to add another board in which I can add the A/B tests (as F.E. features). User stories for one sprint can then be added to a specific sprint for my team (which consists of a few specialists and a developer). This way I am able to overview the status (research phase, test , code writing, running, analysis, etc.) of all tests in one overview. I have not been able to find out how this is possiblie within Azure Devops, or if there is a work around. Can anyone help me?
My team also works in projects other than A/B tests, which means we cannot use the boards section.
Unless there is a hidden way to add another board to a team?
You could Copy or clone a work item to add the user stories or tests to a new boards. Open the user story you want to clone, then click Create copy of work item and choose whether to include exist links, attachments and child work items. After creating, change the Area and Iteration to your target boards.
Update
In Azure DevOps you can only create boards by creating a team. The team board is created as a side-effect of creating the team. Please refer to Manage and configure team tools and Configure and customize Azure Boardsfor details.
After creating and configuring a new team, you could see the boards in the dropdown list.
I set up my first AzureDevops organisation by starting with the Agile process but later changed it to CMMI for the organisation to better align with the other projects my team works on. I think this is where the cause of the problem is but can't figure out how to address it.
PROBLEM:
I cannot see in the backlogs any of the Epics I created. The Epic selector in the dropdown menu of the backlog navigation is present and selected. Some of the Features can be seen in the Features backlog, however, not all.
WHAT I TRIED TO DO:
I created a query from the Epics backlog and tried changing its filters and got to see all the epics if I change the filter from having several OR statements on the Area Path filter to one with Area Path Under "top level area path".
I am 100% sure this is because I changed the process. Would appreciate if someone could please let me know some troubleshooting steps to address the issue?
Thank you
Is there a way to share Epic/Feature/Stores between Team.
We have the Following Teams
1) PM, BA, DEV, Testing for most of the projects.
For a given userStory that might be tasks that are done by BA and only visible to them. But when their work is completed for that user Stories DEV team will pick up and create their own Task for that same user Story that BA team worked upon.
Similarly, when the Dev Task is completed Testing team will create other Task under that story.
How do i organize such a setup in VSTS so that I don't have to duplicate user stories/epic and features between team ?
In VSTS, you probably want to define your own workflow stages, which will be the columns on the Kanban board view. Your stages sounds something like Analysis, Dev, Test, etc.
This way, as each team member wants to progress the task, they will update the work item to the next work stage and likely reassign the task to a new team member.
See these articles for more details (which provide an example workflow very similar to yours):
https://www.visualstudio.com/en-us/docs/work/kanban/add-columns
https://www.visualstudio.com/en-us/docs/work/kanban/kanban-basics
The simple way is that you can change work items’ area to the corresponding area of other team.
If you want to achieve other teams can see the related work items too, you can create a new area (e.g. SharedArea1) and assign to these teams. After that, you can change related work items’ area to that area (SharedArea1)
Team admin page (add another area):
This article may benefit you: Multiple teams