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.
Related
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.
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.
I am new to azure devops and devops field. I am exploring myself in azure devops, where learning boards. I I was confused while updating the status of my work item. I was assigned with a task (example: create a login page. Now i went to azure boards and its allowing me to edit the title and priority fields. Those are already set by my higher levels. I only need to add details like time efforts, status). What security is our team missing to achieve this?
Also i need to move the work items from one stage to next stage(Todo to completed) via VS2017. How to achieve that. Now i am currently going to devops portal and drag and drop the workitems to next columns.
If you have permission to edit a work item, you can edit any field on the work item. This is by design. Whether it's a limitation or not is up to you to decide.
You can update the work item state from Visual Studio by linking it to your commit in the team explorer. Refer to the documentation.
Within Azure DevOps Server, is there a way to limit the work items that can be tied to a given pull request to only those in the current project? Currently, when submitting a pull request Azure DevOps Server suggests and allows all work items within the project collection to be selected.
Yes there is a way to limit the work items from another project to be selected in current project. You can change the View, create, or modify work items Permissions within an area path. Check Restrict access to view or modify objects
So Let's say there are Project A and B. And Restrict work items in Project B to be selected from Project A. In order to achieve this, you need to set the permissions from Project B. Please refer to below steps:
1,Go the Project setting for Project B --> Click Project configuration under Boards --> Click Areas -->Click the 3dots of the root Areas of Project B --> Click Security
2, In the Search Box search for Project A team(or any team that includes all the users in Project A, if there isnot one, you can create a team in project A to include all the users.). Then set the permission to View work items in this node to Deny.
Then any user in Project A team willnot be able to add the workitems from Project B in a pull request.
Above steps will cause some problem if a user is also in other project team. But you can override the inherited permission for this user by following step 1 to allow the the view permission for this user.
If there are many projects in your collection, you have to set repeat setting above permission for each one of them.
However you can submit a feature request(click suggest a feature and choose Azure devops) that restricting view workitems permission in a Project Level to Microsoft Development team. Hope they will consider implementing this feature.
Is it possible to add members in bluemix track&plan with read-only access?
I want to limit the number of people who can add/modify work items into my project.
I understand your question that you want a more fine-grained access control for project members.
Can you not allow project members to edit work items? A short answer is no.
Check official website: https://hub.jazz.net/docs/projectadmin/
Project members have the fewest privileges and responsibilities. They can do these tasks:
- Add and edit work items
- Create Git branches for Git projects
- Create tags for Git projects
- Push and pull source code from the repository
- View and edit pipelines
- Add, edit, delete, and run pipeline stages or jobs
I think project members should have the access right to edit work items.
Bluemix track&plan is based on RTC(Rational Team Concert). I've been using RTC for team's project development for several years. It can be disturbing when someone removes a tag used in a query or changes work item to an incorrect status.
But the essence of track&plan is for team collaboration. Work item is critical to provide transparency and real-time status. Everybody on the team should have the right to add comments to the work item. My best practice is to use daily scrum meeting to review team dashboard and validate the work item status.
In real life, I seldom see team members deliberately update work items that don't belong to them. Instead, scrum master needs to motivate team to provide more update to the work items.
If you want to share the status to a stakeholder who's not in the project team, one doable option is to set your project as "public".
Try to access the link I created: https://hub.jazz.net/ccm51/quickplanner/jazzhub.html#items:projectId=_9b859SQ7EeesKZSRjqyxIQ&serverId=hub.jazz.net&planType=allwork&allIterations=true
Steps to set up your project as public:
1. Navigate to the Track&Plan dashboard. Click "Settings" icon
2. De-select "private" project checkbox & save