TFS 2015 Agile: limit permissions to change states or move sprints - tfs-2015

Is there a way to set user permissions to restrict changing states (status) or moving items from one sprint (iteration) to another in Microsoft TFS 2015?
Appreciate the help!

"Changing the state of the work item" and "Moving the work item to a different iteration" are both examples of a more generic permission - Edit Work Item. It is defined on area level in TFS. For a specific area path you can deny "Edit work items in this node" permission, and the user won't be able to
Change the state of work items in this area
Move the work items in this area to a different iteration
Modify the work items in any other way
First two points is what you aim for. The last is probably not. If you need to granular permissions on a field level, I am almost sure it is not possible.

Related

Work Item Query Policy to check workitems match on merge

With our TFS 2015 source control we require developers to check-in changes against work items.
However, we've had a couple of instances where a developer has checked in against one work item within our development branch, but then when merging to our QA branch they've checked in the merged changes to a different work item. An example of this is where a bug has been created underneath a PBI, the changes in dev have been checked in against a task under the bug, but then merged to QA against the PBI itself. This causes us issues with traceability.
I've seen that it's possible to add a check-in policy of "Work Item Query Policy". I'm just wondering if there is a way to write a query that will determine if the work item of a check-in after a merge matches the work item of the source changesets? I'm not necessarily after the exact query (though it would be lovely if someone could provide one :) ), really I'm just wondering whether it's possible or not to have a query to do this - i.e. is the information available to queries in TFS?
You can't do this with the existing policies, you'd need to build a custom policy.
So, technically this is possible. You can access the VersionControlServer object through the PendingChanges object:
this.PendingCheckin.PendingChanges.Workspace.VersionControlServer
You can use that to query the history of the branch in question and grab the work items associated to the check-ins in that branch.
You can check the associated workitems to the current workitem:
this.PendingCheckin.WorkItems
You could probably even provide the option to auto-correct by adding the correct work items to the checkin upon validation.
One of my policies provides an example on using the VersionControlServer from a policy.

Section Access In Qlikview

GOAL:
-To allow the manager to only view the all projects in qlikview, and not edit anything.
-Team members can only see data from projects they are in
CONDITIONS:
-Joe(Team member) can only see data from his projects only.
-Bob(Manager) can see data from all projects in the team, however he cannot edit or make changes to them.
In this scenario, there is only 1 manager, an admin, and many team members.
So I guess the process would be:
Check who the user is (Not sure what to use here. Username/password? Ideally it would be the company email, but don't know if this is possible)
Once it knows who the user is, checks if said person can access the document
If they do have access, it decides what can be accessed. (if manager, can only view all projects, if team member, can only view certain projects)
Display the dashboard.
Right now, the QVW file gets data from a database using OLEDB connection.
Sorry I've only been introduced to Qlikview about a week ago and I've been tasked to get this done so any help would be great.
Thanks.
You can find a lot about QV section access around.
Think your scenario is possible to be achieved using section access. Please read https://community.qlik.com/docs/DOC-1853 for more detailed explanation of section access methods.
Warning: Always have copy of the document without section access!
Just to be sure you are not locked out of the document because if this happens there is no way to open the document

Permission to activate an Iteration in TFS 2013

I want to give permission for a specific user in my TFS project to do the following.
Create Iterations
Edit the Iterations
Activate the Iteration (In simpler words, 'tick' the Iterations so that they can be seen by others in the team)
MSDN says that
To create or modify areas or iterations, you must either be a member of the Project Administrators group, or your Create and order child nodes, Delete this node, and Edit this node permissions must be set to Allow for the area or iteration node that you want to modify. MSDN
I do not want to give Project Administrator permissions to this specific user.
Hence I gave the following permissions to him in the Parent Iteration.
permissions - screenshot
When logged in as the specific user, TFS says that
You do not have sufficient permissions to configure iterations for this team. You must either be a team administrator or a project administrator.
However, the User can do the following.
Create Child Nodes
Edit the Start/End Dates of existing/new iterations
My question is:
Is there any other way to give a user the permission to 'tick' an iteration without giving him 'Edit collection level permission' or 'project admin permission'
You can create a new TFS group under your team project. Then, grant that group "Edit Project Level Information" permissions. This will allow the user to check the tick box to make the iteration show up in the backlog task board.
What I did was create a "[TEAM PROJECT]\Project Managers" TFS group, I granted that group all permissions on the root node of both the Areas and Iterations. And I also granted that group "Edit Project Level Information." My user was then able to manage areas and iterations - including the "ticking" to activate the iteration.

Need assistance with removing "Backlog Iteration for this team" designation in TFS 2012

I have a quick question - I erroneously selected the "Backlog Iteration for this team" designation while setting up a child iteration in TFS 2012 web access (right clicking on the Iterations admin page). I cannot find any way to remove this. I can move it to a different iteration (I don't want to do that) but I cannot figure out how to completely remove it altogether. I do have admin permissions.
Is this something I can remove in Visual Studio instead?
Any assistance you can provide is appreciated.
Maybe too late for this but if you go to the parent node of the selected iteration and select it that will make the magic :)

Sharepoint workflow association for specific list item not for entire list

I am using sharepoint visual studio workflow and want to associate with specific list item. workflow should only visible for that item. How can i get this done. any ideas??
Thanks in advance!!
This is impossible. You are apparently missing the idea of workflow. Workflow definitions are not item-specific. They are supposed to represent reusable, configurable pieces of business logic that can be arbitrarily (either automatically or manually) executed for any given item (or document) in a list (library).