I'm struggling with understanding if it is possible to hide certain tabs from TFS web interface based on specific user group. What I'm looking for is to hide Build/Release , Code tabs and if it is possible the configuration option (the gear button). From what I could find there was a "WorkItemOnlyView" default security group in previous versions of TFS that looked like what I wanted. Is it possible to accomplish something like this now?
You could make them "Stakeholders" access which removes their access to code/builds/release entirely in web portal. Then should see the web portal such as below screenshot:
Another way is restricting access in VSTS and TFS.
Related
As you know, in TFS 2013, from a permissions point of view, we have 3 licences available to us:
Stakeholder
Basic
Advanced
As far as I am aware, Advanced is the only way of accessing 'TEST' area (Test Case Management), however, is it possible to create 'custom' security licences as we would like to give access to certain users to the 'TEST' area but not have them access other areas where they can create other WITs or potentially modify open WITs - We just want them to be able to view and run Test Cases + create a BUG where required.
We are using TFS 2013 On Premise.
No, we cannot achieve that. We cannot custome the access levels to add/reduce the supported features for each level.
For TFS 2017 and earlier versions, you should assign the Advanced
level to those users for whom you've purchased the full Test feature
set.
Advanced access level include all Basic features. And TFS doesn't provide a more granular permissions settings. So we cannot restrict the users who in Advanced access level to only view and run Test Cases + create a BUG. That is contradictory. We can only set the user permissions based on the existing options.
Please see About access levels; Change access levels and Permissions and groups in VSTS and TFS for more information.
Not exactly like this - How to publicly share a Visual Studio Online Repository? - I am trying to share the source code repository (Git) from Visual Studio Online to registered stakeholders. They need to get at the latest stuff at the Master branch to eval it along with work items. How can I do that?
Thanks.
If you have people with a Stakeholder license they won't be able to see the code. The Stakeholder license only gives access to:
View team dashboards and portfolio backlogs
View, add, and modify items on the backlog
View, create, and modify work items such as stories, features, and bugs
View, create, and save queries
Create and receive alerts when changes are made to work items
Submit, view, and change your feedback responses.
For people to see the code, they will at least need a Basic license. If you then want to restrict their access, you can do so by creating a TFS Group and setting the correct permissions. In this case, you want to limit the Code permissions to only Read so they can't modify the code.
See Permission reference for Team Foundation Server for more information.
This means there is no free way to allow users to read your code. You do start with 5 free basic licenses however, so if that's enough you can assign those to your users.
How do I share artifacts (e.g diagram and docuement) across the entire project, not just at issue level at JIRA? Something like a common area for posting information.
A couple of possibilities spring to mind.
Firstly you could use the HipChat integration. Sending messages via comments to a team HipChat group.
Another option would be to create a generic JIRA user with an email address that is a mailing list for your team. That way you can use the Mentions functionality to inform everyone of something.
More about the mentions functionality here: Atlassian - Using Mentions
Use an Epic in the project
If you are using Jira Agile you can simply create an epic (called Documentation) and house all of your documents in the epic itself or group documentation by creating subtasks in the epic to essentially create "folders". To ensure the team is seeing any changes add them all to the "watchers" list.
Use a Confluence Space
If you have access to Jira Confluence, just create a project space and create or link your documents there. Another benefit of using confluence is you can make these documents available to external customers (no need of a Jira account). To ensure the team is seeing any changes add them all to the "watchers" list.
Creating a Space
https://confluence.atlassian.com/doc/create-a-space-139463.html
Use a Project Dashboard
Use a dashboard and ask that your team pay attention to this every day. Dashboards are a great way to propagate information to distributed teams.
Customizing the Dashboard
https://confluence.atlassian.com/jira/customizing-the-dashboard-185729498.html
Can we add/modify the filter of the boards:
Work/Backlog/product backlog/board(the stories/backlogitems)
Should be able to filter the Iterations/Sprints
Work/board(tasks)
Should be able to change the Areapath filtering
Is there any way to change the default filter and/or add quick filters?
As per this post, you can't really amend the underlying
query for the task board:
How do I change the underlying query for the task board (and backlog board) on TFS Preview
Although as mentioned the tags in TFS 2012 Update 2 can help.
However we achieved something similar to what you are
asking by creating a team per product.
In the web control panel for your team project, create teams (and area paths) for
each product you are interested in.
In the control panel, for each of these teams, you can set which
iterations are associated with them. So for a particular team,
you associate only the iterations you are interested in for that
product.
You are then able to switch between teams via a drop-down at the
top-left in the TFS web interface (you will need to use Browse All
originally.)
See Multiple Teams with Microsoft Team Foundation Server 2012 & Visual Studio Scrum V2.0 for a good reference for this.
The Work Item Tagging feature in TFS 2012 Update 2 can help.
Other than that, you can write your own plugin.
We're using team system to control our developement (product backlog items, sprint backlog items etc). It's a pretty nice tool but we wanted to allow other users to be able add bugs and new feature suggestions WITHOUT letting them mess with the actual development bits.
I can set these guys up so they add the work items they need but I can't see a way to block access to the bits I don't want them to edit/view. Has anyone else seen this? Has anyone found a solution?
Are you using TFS 2010? If so, you can simply add them to the Work Item View Only Users group. This will grant them access to create new work items and to view/edit any work items they've created (but not others). Check out this link for instructions.