everybody. I've the following issue, when someone makes a new pull request and I leave certain comments, if this someone, does update the pull request, TFS instead of moving my comments with the code changes, it is left on the line number, rather than the code snippet.
If someone knows how this to be fixed, as it cause enormous efforts to track if the issue was solved.
Thanks for reporting this issue.
This is a new feature that is only available in TFS 15 RC1 and VSTS. Older servers do not have this feature. This feature is called comment tracking and it is mentioned in the release notes here.
When you click to add a comment as the screenshot below, you would be able to add a comment for a line of code:
Then you'll see your comment under the line:
Related
Is there a way to reset or start over with the latest version TFS work item template? I do not care about any existing work item history.
Scenario: I have a TFS project that has code, but never used work items. The existing template is too old to use the automatic Configure Features wizard tool. It is ok to mess up any work item history.
Is this possible? Thank you!
Have a look at TFS-PowerTools
The built in Work Item Templates should override your existing ones. That might even work before updating, but i'd not recommend that try.
We had this trouble once too. A coworker fixed this after doing some kind of Troubleshooting guide. (Let me check tomorrow if i can find that one again)
Let me know if that helped!
Take a look at https://nkdagility.com/tfs-process-template-migration-script-updated/
It covers off what you need to do, and includes some PowerShell to help you.
I created a task on jira (agile) by using kanban board but, I couldn't move it to "in progress" column. Finally I found the solution. You can see the problem and the solution step by step via pictures.
The problem is this:
Follow the topic to find the solution.
Just follow the steps. if you know a better solution, please share it.
The solution is:
Go to administration panel, open integrity checker, select all and click to Check.
Select Fix all and click Fix.
You'll see the fixed issues. Then click OK.
Finally you can do anything with your task again.
Now follow the pictures.
step 1
step 2
step 3
step 4
Please note that the usual reason for this problem is that the Conditions in the workflow are incorrect and the user does not match the rules set by them.
The problem answered by the main answer here only applies when you have corrupted data.
It also neglects the fact that you should treat corrupted data as a potential problem that you should investigate - it will be caused by crashes, or broken add-ons or scripts and you should track them down and fix them.
How to link the issues in Bitbucket?
I already use the milestone, component and version fields, but i need to mark issue as depend on #125 or blocked by #1220.
How?
Update
I can place link #1 in issue comment, of course, but:
Comments are scattered throughout the whole issue log.
Linked issue doesn't knowing about it.
So, I've search for linked issues\tickets fields, like Bugzilla/Mantis/OTRS do. Or Linked and Related in Stackoverflow itself.
UPDATED
Simply use the # and BitBucket will link automatically to the issue, as you know.
The linked issue isn't aware it was linked (as on GitHub, for example): it's the BitBucket behavior.
We're using TFS for our day-to-day work management, but are currently unable to use it for source control - we're using SVN instead.
I would like to nonetheless ensure that all our work items have been code reviewed before being closed, and that any code review actions have been followed up on. Any recommendations on how we can keep track of this using TFS with minimal manual steps?
I am also concerned with ensuring that the code review step has not been skipped, and auditability of whether it has happened and whether all resulting actions were closed off. If I look at a closed task, how can I easily tell that a code review occurred on it?
(Optional) Require that every SVN change refer to a work item number in TFS with the check-in comments.
The work item in TFS has a "LINKS" tab on it. As soon as the code is checked in, another work item of type "Task" (or whatever you want to use for code reviews) should be created and linked to the primary work item on this LINKS tab to request the code review for that work item. It should refer to the SVN revision number(s) that need(s) review.
I'm not very familiar with SVN, but I assume there is a way to have branches that could be used as follows. Maintain a separate branch for reviewed code. Only code reviewers can merge into that branch. The only way code can get in there is if the proper work item in TFS exists, and a code reviewer approves and merges the code for it. I'm used to Mercurial and TFS where merging code is really easy. If merging is not easy in SVN, a different solution may be required.
If the linked task exists on a work item, then you know that the code has been checked in and code review is in process. If the link exists, and the linked work item is resolved, then you know the code review is complete. If the link does not exist, then you know that code has not been checked in for this work item (or at least it's not in the reviewed code branch, and has no intent to be there).
We have decided to edit the TFS workflow to include an extra 'In Review' state after 'Resolved'. This allows us to use the existing task board without any overhead of creating separate review tasks, or having to edit the task title to be 'in review: ....
I'm using the Build Explorer to delete our project's builds. It's taking forever because it's 'timing out' trying to delete the label and drop location (now that the drop location doesn't exist any more).
So, I'm hoping to do this via the command line to see if I get more love.
Is this possible?
Yes it is, see the following HowTo on MSDN.
How to: Delete a Completed Build (Command-Line)
However, I'm not sure that this is going to improve the situation for you as it basically does the same server calls that the UI does. Give it a try anyway. In the meantime I'll go ask a few folks and I'll edit this answer if we come up with anything to help you with your timeout issues.
The TFS Build Manager utility will let you multi-select and delete. It still works serially but at least it's only one manual step.