I can't see where to activate User Stories for my DevOps. I only have Epics and Issues. Where can I change this?
Backlog elements are dependent on the chosen project process as project creation. The backlogs defined for each default process are:
Agile: Stories, Features, and Epics
Basic: Issues and Epics
Scrum: Backlog items, Features, and Epics
CMMI: Requirements, Features, and Epics
As seen in the official documentation, the process implemententing Stories in backlogs is Agile. You have probably set up your project as Basic.
To change this, you need to go to the Organisational settings and then change the process.
Microsoft has a page exactly dedicated to this exact change with clear defined instructions with screenshots:
Changing Process from Basic to Agile
For further projects, just use the process Agile and it will be available as default.
Related
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 am evaluating Azure Boards / Azure DevOps and I wish to restrict what a Stakeholder (in this case, a customer) can see and do.
I have managed to limit what a Stakeholder can do, but is it possible to completely hide the Pipelines, Artifacts and Project Settings panes from Stakeholder?
Se the image. I want to completely hide the panes marked in red.
Image of panes to be hidden
I am not sure if we can show/hide the DevOps Services in top-level, based on a specific role. This is only available for the project level.
https://dailydotnettips.com/turning-azure-devops-service-on-or-off/
and these settings can only be controlled by the Project / Org administrator.
We cannot get rid of the Pipelines from the view for the stakeholders. Yes, we can turn off the pipelines service from the project settings overview page, thus the pipelines node will disappear from the view. However it's applied to entire project, that means all other users also cannot see the pipelines.
As a workaround you can manage security for all pipelines and Artifacts for each project, just deny all of the related permissions for the stakeholder.
In addition, I found a related suggestion ticket, you can follow and vote this ticket to get the latest news.
I'm trying to configure and customize the Azure DevOps tool as per the requirement for my application development team. In the boards setting, I have selected the option "Bugs are managed with Tasks" to get a good view of my sprint items. However, my team reports post production issues as Bugs in the tool and enabling the above mentioned setting doesn't allow me to view these Bugs in the Kanban Boad. Reason is they are not linked with any User Story.
I have been exploring the options in Backlog levels options available in the Processes settings and found that the Backlog level "Stories" is tagged only for User Story.
My query here is can i try linking Bug and Task to the already existing "Stories" backlog level. Azure DevOps does gives option to create a custom backlog level and custom Work item type. I would like to customize the existing functionality to best fit my team. Please let me know if there is a work around.
Query regarding Backlog Levels in Azure Devops
This behavior is by designed and there is no way to fix it at present for the exists Work item type Bug.
Because there is only one requirement backlog and it cannot be removed, but can be renamed and edited:
There is an user voice about this request on the Developer Community.
As workaround, we could create a custom the Work item type and add it to backlog level, for example, I create a custom Work item type BugWithoutTask, then add it portfolio backlog:
Then go to backlog settings and enable new backlog:
Now, we could these BugwithoutTask in the Kanban Boad:
You could check this document for some more deails.
Hope this helps.
what do i need to configure to show on what board column my tasks and bug is located in Azure DevOps. Currently it only displays on Epic,Feature and User Stories only.
It is by design that Tasks and Bugs are not shown with Epics, Features, and Stories in Boards, for Tasks is not of backlog level and it is managed within Stories as child item. For details please check this document.
Hovever you can easily create new tasks, tests and bugs from the a story's board. Please check the document Add a task or set of tasks on Boards. You can check the document for more information about add child items from Backlogs
The operation that is supported by azure devops currently is that you can setup Bugs shown with Epics, Features, and Stories. Please check documents Set your team's preferences for tracking bugs
You can also choose to hide or show one or more backlog level(Epics, Features, Stories) for Backlog navigation. For detailed information please check document Select backlog navigation levels for your team.
If you want to suggest Microsoft to support showing tasks and bugs with Stories and Epics. You can submit a feature(click suggest a feature and choose azure devops) request here.
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