Using Team Foundation Server 2103(Web Access).
Whenever I navigate to Backlogs -> My current iteration, I see the User Stories as well as the Tasks all auto expanded.
What I want is I want to default it to Collapse.
Is there any setting for that?
In an iteration view want you care about is the Tasks (the plan) rather than just the PBI's and this is the default behavior. There is currently no way to change it.
Related
I use VSTS/TFS for work and side projects and I wanted to setup a trigger/rule that would automatically move stories into a certain iteration when I move them from "New" to "Approved" or whatever column is associated with an active state. I know how to change the iteration manually but it would be way easier if there was a way to say something like this psuedocode:
if (workItem.State == "Active") {MoveToIterationActiveForTodaysDate();}
Ideally too, if this isn't too picky, I would like it to only run on initial move so I can reassign to a different iteration later if I wanted to.
If anyone has an easier way to do this too that accomplishes the same thing (moving items to an iteration without having to manually activate the story and move it to the desired iteration) that would work as well. I'm still figuring out the ideal way to manage VSTS/TFS. Thanks in advance
Using VSTS is able to customizable work item rules.
Whether it be automatically setting the value of certain work item
fields or defining the behavior of those fields in specific states,
project admins can now use rules to automate the behavior of work item
fields and ease the burden on their teams.
More details please refer this tutorial: Add a rule to a work item type
However, it works with fields in the work item, not able to move work item to different iteration or area directly.
There is no out of box feature could achieve your requirement with TFS and VSTS for now. You may have to customize TFS events/actions to achieve the same feature as right click the work item--select move iteration--choose iteration.
Moreover, you could also use some 3-rd party extensions/tools such as Giulio
suggested TFS Aggregator.
As of today, there is no built-in automation, so the community wrote some tools that react at TFS/VSTS events and run scripts.
I can suggest TFS Aggregator which is used by many organization throughout the world: I am one of the core contributor.
I am new to Team Foundation Server (TFS 2017). I want to create an additional iteration state called “QA Passed”. Which will be controlled by only Test user. Also, I can see when a particular user login into TFS local web portal then he can see all other tasks in iteration Backlog/Kanban board.
Now how can I
Create an additional state in iteration which will be controlled by
only Test users
Restrict a particular user viewing other tasks and view only to his
specific tasks.
I will be very happy to get solutions on this regards. Thanks.
To achieve that please follow below steps:
For question 1:
Click the gear icon to navigate to manage page
Select ‘Work’ tab > Iterations > New iteration called “QA Passed”
Click the ‘…’ behind ‘QA Passed ’ > Security
Select the Test Users who will control the iteration and set ‘View permissions for this node’ to Allow.
For question 2:
Switch to Areas tab
Click the ‘…’ behind the specific area > Security
Select the specific users and set ‘View work items in this node’ to Allow and Deny for the Restrict users.
We are using TFS to manage our backlog.
The PO believes that items priorities are constantly changing by team members other than her, which is far from ideal.
Is there a way to create a TFS query that tells me who has made the change, when, and if the change was applied to the Stack Rank? In our TFS set up the Stack Rank provides the items order in the backlog.
You can use a team alert or personal alert as Mat suggest,I have add an answer here How to create a TFS alert for changes to the items' Stack Rank field
I have two separate branches created for a project with two users - each user only has access to their branch.
I have created the project backlog items, however each user when logged into Visual Studio Online can see the backlog items - which is ok. However once one user completes an item in their branch, I don't want that item to affect the other user's ability to continue working on that item.
I want to test how each developer creates a new UI on their respective branches. Essentially the work is the same, but the way they implement would be different.
For example, an item may be "Update website front page".
Essentially I want them both to do the same thing but on their own branch. Can we separate backlog items by branch?
Sounds like you have some crazy Hunger Games development scenario going on and as Daniel said, better to develop in one branch and merge to the other.
However, if you want to restrict Work Items across Teams or TFS Groups then you can restrict the Area Path. So, either set up a team for each developer or simply create an Area Path for each branch and set security on it.
Have a look at Customize area and iteration paths and the section on "Set permissions to restrict access to work items"
I am setting up a tfs 2013 environnement,
In a Scrum team project, we would like a few users to be able to create backlog items and tasks, but we would like that other users to only be able to change the task their are assigned. Or at least we would like that these users can modify existing tasks, while not being able to create new one, or move them to other sprints
at this time, with the security parameters i have found, i can only either allow a user to do everything (create and move a backlog items from a sprint to another, modify it, delete it...), or nothing (if you can't create or move, you also can't modify an existing one...)
any clue how i could proceed ?
We have custom work item types and we prevent users from creating certain work items by editing the WIT's xml and including this in the transition between nothing and the "New" state. [global]\TeamSystem-TaskCreation is a TFS security group with a limited set of members.
<TRANSITION from="" to="New" for="[global]\TeamSystem-TaskCreation">
There is no real way to do this I'm afraid. TFS does not have many fined grained access controls, the impression I get is that it is designed to empower people and not restrict them.
You should be able to ask people not to change tasks, if that is your way, and use the Work Item History and/or Alerting functionality to know when they have done something you don't want them to. For example, and task changes not by approved people sends and e-mail to the leads.