We started to use MTM 2010 for creating and publishing test cases in TFS 2010. Unfortunately, users are not able to publish test results due to lack of permissions.
I do not want to grant code access to testers. Currently, they have only “View project-level information” permissions. Could you please advise what (minimal) permissions should I grant to testers so they can run test from MTM and publish the results?
You should grant following project level permissions to testers, beside permissions they already have:
“Create test runs”
“Manage test configurations”
“Manage test environments”
“View test runs”
Also, be sure that in Area security for specific projects, testers do have “Manage test plans” permissions, beside permissions you have already assigned to them. If you want to be sure that testers do not have access to code, you can always set Deny permissions for specific files in project.
Related
I'm currently developing a gmail add-on and am hoping to allow a few users internal to my team to test out the add-on prior to a public release. I was following the documentation here from google that states
You can allow other users to test the add-on by sharing the Apps Script project with their account (read access is required) and then prompting the users to follow the above steps.
I assume that 'read' access is equivalent to 'view' access, and have given a user 'view' access to the project.
The problem I'm running into is that even with 'view' permissions, users aren't able to do a test deployment and install the add-on to their gmail account. The blue 'Deploy' button simply isn't visible. Any ideas on how to get my add-on into a few users hands before publishing, but without giving them edit privileges?
One way to do it is to have the users copy your script and deploy it.
Another is to publish the Add-On privately and you would have control over what version of the Add-On your test users are seeing. For this your users should be of the same Google Workspace domain
I am using TFS 2018 update 2 version, and I have to implement continuous integration for a project.
For that, I need to add code review functionality before "check in" as a check in policy, but in TFS 2018 version, there is no such policy?!
Question: are there other ways to include "Code Review" as check in policy?
(We are using TFVC, not GIT).
To prevent check-in without a review, you can use a check-in policy. Here's a custom check-in policy that requires code review before check-in:
https://marketplace.visualstudio.com/items?itemName=ColinD.ColinsALMCheckinPoliciesforVS2013andVSO
Install Instructions:
Download the VSIX and install it.
In Visual Studio 2017, connect to VSTS or TFS and connect to a TFVC repository.
Open Team Explorer and click on the Settings tile.
In the Team Project section, click the Source Control link.
Click on the Check-in Policy tab.
Click "Add..." and add either Code Review Policy or One Work Item Policy
Click either policy and click "Edit..." to open the configuration page for the policy.
But I should point out that check-in policies are not security mechanisms, think of them as a reminder for the developer to send the code for check-in. Developers can easily override them.
If you really need to prevent any check-ins, you should deny check-in permission for developers, and have them send their changes to the manager using a code-review (or shelve set). The manager can then unshelve the changes and check-in after reviewing.
I want to add Device.Read and Device.Command permissions to Graph Explorer. When I open the permissions and add them I'm told I need admin approval, although these specific permissions do not require approval. I want to add these permissions without taking away existing admin approvals. How do I do this?
I have 14 people in 5 teams. Some are overlapping. i.e A couple of Web team members are part of the Server team.
I am not sure if this is the right way, but I would like to manage each team with their own Jira project.
Thus, I have 5 projects:
Mobile
Design
Web
Server
Hardware
I would like to assign access to projects based on Group. i.e. Mobile project should only be accessed by a Group name Mobile Developers. Design project should only be accessed by the Design Team Group. Design should NOT have access to the Mobile project.
How do I accomplish this on Jira Cloud?
Currently I have two Permission Scheme:
Default software scheme shows all 5 of my projects. I can only edit the Name and Description. When I click on Permissions it takes me to a screen that says:
How can I assign permission to each individual project based on Group?
Clone your default permission scheme and create a custom permission scheme for each project.
For example:
Mobile Project Permission Scheme
Next, assign the new permission schemes to the projects. So the Mobile project uses the Mobile Project Permission Scheme, the Web project uses the Web Project Permission Scheme, etc.
At this stage, there is no new behaviour as all the projects are using the same permission scheme, just they now have their own copies of the scheme. That means any changes you make to a custom permission scheme will only impact on one project.
Now, edit the permission schemes and give permissions based on the groups.
e.g.
Manage Sprints - Mobile_User_Group
Navigating to a project page of a TFS 2013 collection by Administrator account returns this error:
http://server:8080/tfs/DMS/ProjectX
Error
The page you are looking for is currently unavailable.
TF50309: The following account does not have sufficient permissions to complete the operation: Administrator. The following permissions are needed to perform this operation: View project-level information.
The modification of TFS administration console is also disabled as is seen in this screenshot:
How can I grant full access to this team project collection?
Administrator accounts do not automatically get TFS Administrator capability and it must be granted explicitly.
You need to speak to your TFS Admin and get them to grant access to your account.
If you are the TFS Admin you need the account that was used to install TFS.