I have installed TFS2012 on my server, now I need to achieve change tracking.I have explained the details below.
The whole idea of change tracking is, if I change the PBI/Requirement the all linked work items/bugs/impediments status should be changed or TFS should notify me in some way.
TFS will not automatically update one Work Item when a linked item changes. There is no functionality for that out-of-the-box. What you can do is configure an alert.
Or you can test whether the TFS Aggregator that exists for TSF 2010 (open source project) will work for 2012 (not officially supported). It can update child or parent work items when a workitem in the hierarchy changes.
What you want is not possible in TFS out of the box, but you can implement this with relative ease using a custom ISubscriber or a SOAP webservice. See the following answer on question regarding this.
Related
I have a requirement to update work item status to a ready for test state after the first successful release using TFS release management. It seems like there should be a straightforward built in task to do this but I can't see it. My current thinking is
Use TFS REST API to query the workitems and update them all using powershell
Wrap this up in a powershell task and include in the release definition
This will do the job I reckon. It's yet more powershell in our releases but they are built on a stack of powershell anyway so at least it's well known.
But is there a better (quicker) way to do this? If the answer is a straight 'no' then great - I will accept that answer gladly.
We are on TFS 2015 R4.
Many thanks for any/all help
Sorry, there is no out-of-the-box feature for this by Microsoft.
But we still could use some three-party extensions or tasks to handle this situation.
The WorkItem Updater task can update the following work item fields during a build or release:
Update the state for workitems linked to a build.
Update the assignee for workitems linked to a build.
Add the build as Development Link to the workitems.
The limitation is also very obviously, it could only update work items which be linked to a build. Which seems not be a problem, it's also a good behavior track work items during build pipeline.
Otherwise, you have to use the ways mentioned above to update normal work items after/during a Release.
My team is currently using the CMMI board in Team Services and we would like to switch to the Agile board. I was told we can't just change the template, but I can't figure out how to export all of our open tickets to a new board. How do I easily change our team's board. Thanks!
At the moment this is technically not possible. When you choose a Process, during project creation, you can't change it to a new parent later. So you pick CMMI, or Agile or Scrum and later you can only change to a derived template.
What you can do though, is create an inherited process template and customize it until it looks and feels the same as another process template. It's quite a bit of work, but doable.
It is expected that changing from one base template to another will be added somewhere in the future. But at the moment it's not showing up on the TFS/VSTS feature timeline.
There is no easy import/export option either, though there are a few tools, like VSTS Sync Migration Tool that can copy over work items and map them to a new structure. I'll probably just be as much work as creating an inhertited process though.
I have Eclipse Neon with TFS plugin
When I check pending change and I relate to work item
The problem is that the Check in Action by default is Resolve and not Associate
How do I change the default?
All I found online is about visual studio which didn't help me.
(Registry not worked HKEY_CURRENT_USER\Software\Microsoft\VisualStudio**11.0**\TeamFoundation\SourceControl\Behavior #ResolveAsDefaultCheckinAction = "False")
Unfortunately, this could not be achieved in team explorer everywhere(TFS Eclipse plugin) for now.
As a workaround, you could edit the Work Item Template definition for the types of work items you are using (Bug, Task, etc.). Then remove the Check-In Action from the Work Item Template (WIT). Once the WITs have been updated into your team project this will be available for all users. Now when you add a related work item, the only option available is Associate. However, this solution has some pros and cons. Below is a few to consider:
Pros
This change only has to be made the Team Project and nothing has to be done on the clients.
If your team not resolve the work item, removing this option is not a big deal.
Cons
This would need to be applied to all current Team Projects and would
need to update the Process Template for future Team Projects.
This removes the Resolve option for users, so there is no way to perform this action anymore.
More details about how to remove resolve option, please refer DaveShaw's answer in this question: How to disable auto done status for task in checkin
I have a team project previously created on VSTS i.e. TFS online and it has some work items created, now I have on premise setup of TFS 2015. I want to migrate all those work items into my on premise TFS 2015.
Is there any way to do it?
There are three ways to achieve this, it's based on your requirement and situation:
If you don't mind losing work item history, you could just pull over work items, using Excel. Details steps please refer this blog-
-Migrating TFS Work Items to a new Team Project using Excel
(TFS/VSO/VSTS)
If you have no work item customisation, then OpsHub is also an
option.
If you have work item customisation and need keeping histroy ,
then you are going to have to use TFS Integration Platform.
Can I have guidence for TFS 2010 for the following areas:
What is the correct use of tfs and the properties that are exposed for each backlog item and task for recording of effort so that we report on progress using the burndown charts and can assess velocity.
It is not obvious to us what is the appropriate workflow for raising questions about functionality against tasks / user stories so that the person who needs to answer them can easily find those tasks / stories that have outstanding questions. And for when the question is answered how the person(s) who need to know the answer are alerted that the answer is there. Maybe tfs is not the right place to do this and we should be manually doing this?
Unless you customized something, the report features you are asking about will light up in the reports if you use the field in the Task work item named Remaining Work - update it regularly - daily if possible.
The database most of the default reports use (Tfs_Analysis) gets updated every 2 hours by default. Some of the reports only show a daily roll-up so depending on what you are looking for you might not see changes until the day after.
As for your 2nd question about how to communicate about missing information in user stories, etc.. you should read the Process Guidance for the template that was used to create your Team Project. I'm guessing you are using the MSF Agile 5.0 template, so do a search for that and "Process Guidance." The Process Guidance is basically the instructions for how to use the TFS work items and reports, etc... It can be found online (on MSDN) or by right-clicking on your team project in Team Explorer and choosing Process Guidance from the context menu. I'm answering this from my phone but can include a link to it later if you find this helpful.