Somehow I have changed the TFS 2012 query that is used for code reviews. This query can be found under "My Work" in VS 2012 towards the bottom. I can see the guts of the query by selecting "open query" next to the title "My Code Reviews & Requests" and then selecting "edit query". However, it is not possible to save this query in a way that will change the "My Code Reviews & Requests" or at least I can't see it.
The issue that I have is that someone the query has been changed from the default and I don't know how to get it back to the default. This issue is isolated to me and this specific TFS instance. I can connect to a different TFS instance and see the default query using the same steps as above so I am relatively certain that this issue is related to a specific TFS instance and not my local machine.
Try voting on this Microsoft bug to see if it pushes for an improvement in TFS design by allowing more control over the queries generated by the My Work view:
Queries listed under My Work cannot be corrected
You don't mention how you change that so as I guess you customize the process if so? Of course this happen to existing project but as I guess it will not happen for new project??? if so you can download the existing project that has the issue and create new project using the same process template and try to compare the 2 process to know what is the different and how you can change that.
Related
TFS 2012 Checked out by someone else or in another place.
Is there a way to see by who this change is checkout?
I know, because the source code has not been published to the server yet, there's no way to fetch the changes made by that person. Aldo is there no way to get to know who is working on it?
Yes, i can ask arround in the team who is, but we have several teams in different offices.
So its not that obvious...
Yes, there are multiple ways to see who has a file checked out. The mentioned TFS Power tools are one way. Another is to use the commandline tools:
tf status $/TeamProject/Path/To/File.ext
You can use TFS Power Tools (Visual Studio Add-in) and do a search "by Status"
That will show you which items are checked-out, by who and in which workspace.
I found a work-around to get this information, though this procedure may not always be possible. The check-out log shows the list of users who have the file/files checked out.
Right-click on a file/folder and choose Check Out for Edit. In the Output window (if not visible, go to View > Output), you should see something like this:
$/Dev/SharePoint/Finance.Sandbox/Resources/GlobalResources.resx:
opened for edit in TGTRAPP22155;Nigel.Hewitt
opened for edit in SRCGAPP21921;Bob.Carlo
opened for edit in ARSYAPP22182;RDP-ADMN-Jane.Pierre
This should tell you the name of the user and the machine on which the file has been checked out.
(To undo your own check out operation that you just did to get the above information, right-click on the same file/folder and choose Undo Pending Changes. If prompted if you want to "Undo check-out and discard changes?", choose "No to All" to preserve your existing changes and only roll-back check-out on files that don't have changes.)
In Microsoft Visual Studio 2012, there is a pretty good TFS (Team Foundation Service) and in this TFS, you can request code reviews of your work among your peers.
The bad thing is that if you have already checked in your code, it complains and it does not allow you to issue a code review since it sees no changed in the code you have been working on locally.
How do I issue a code review in TFS after I have already checked in code? Can I do it somehow as a comparison to a set of code I checked in earlier? If so, how?
You can right click on a changeset in View History and click Request Review.
There are also links from the View Changeset panel in team explorer.
This has been asked before but I'm struggling to find a way to delete a work item in Team Foundation Server. This looks promising:
http://devmatter.blogspot.co.uk/2009/04/deleting-work-items-in-tfs-ui.html. But no luck with it so far.
First tried the following command:
witadmin destroywi /collection:"https://<<my TFS collection>>" /id:1223
It returned Unable to destroy work item(s) 1223. TF237090: Does not exist or access is denied.
Unfortunately I can't download the "Delete Work Item" utility mentioned in the article due to work's internet restrictions as it's on Skydrive. Also tried the "TEK workitem" extension (mentioned in a comment at the bottom) but this won't let me either as I'm not a Project Collection Administrator.
Am I doomed to be stuck with this work item forever or is there any other way?
Yes it's a little annoying. Setting the item state to "Removed" will at least hide it from view.
The SharePoint install is a SP2010 install on a 2008 R2 server. Everything is fully patched. I am running the SP Designer on the SharePoint Server directly.
I have a workflow which is intended to send an email when a new document is created in a custom list. I have deliberately kept the workflow very simple in order to illustrate this problem.
After creating this single step workflow in SP Designer, I click "Check for Errors" and SP Designer reports "The workflow contains no errors".
I then click "Publish" but the Workflow Error dialog is displayed with the message
Errors were found when compiling the workflow. The workflow files
were saved but cannot be run.
Clicking the advanced button reveals more information:
Could not publish the workflow because the workflow configuration file
contains errors
Any suggestions gratefully received
I'll share what fixed it for me - deactivating all workflow features at the site collection level (that is, Workflows, Three-state workflow, Publishing Approval Workflow) and then reactivating the features. I was then able to publish my workflow. This post helped, not sure whether this only works for 365 though, but it's sure worth trying first if you are considering a reinstall.
after googling for quite some time, i think it's an authentication issue. How is your SharePoint set up? Do you use HTTPS for authentication? If so check out this article.
I know this error message from sharepoint. I got this by dealing with multiple lookup fields refering to other lists. Even when I check the worfklow for errors SharePoint says that its all fine but i can't publish it at all.
Try to build a new Test-Site on your Site Collection. Build a Custom Document Library, leave it standard and then set up a new simple workflow just sending a mail.
Fill out the needed fields in mail only using simple values. Send to your mailadress, simple mail subject and simple mail body.
Set the workflow to run only manually.
Try to publish the workflow.
When this is working, then compair to your existing workflow and change your values by trail and error.
After doing a clean install of the OS and SharePoint, workflows are working flawlessly. I can only conclude that the problems were caused by left over registry settings from MOSS 2007. Thanks for the suggestions that people made.
This could also happens if you chage the URL of the web application, all you have do is click the Design button from the library itself.
when changinf the URL from http://server/Site to example: http://server.xx1.net/site, and you try to publish it tries the old url.
what helped in my situation is changing from start workflow automatically to manually.some times answers for critical situation is very easy. hope it helps, many thanks
I ran into this problem and after digging for days and folks suggesting to rebuild the servers, disabling and re-enabling site features, remove previous workflow versions, etc. and trying everything except rebuilding the servers (not practical for clients production environment). I decided to try some tests and found that this issue was only happening on one particular list no matter how simple or complex the workflow was... And when I would check the box for start automatically on item create (or when item changed) it would fail to publish and give the error above, but if I published it with just manually start worked fine. Finally after deleting views and some more testing, I discovered that there was over 240+ columns in this list (I did not create it...) and 50+ workflows set to run on create... Thankfully I have a test environment I built out for the client so I sync'd the Site Collection database back to test environment from Production re-ran my tests and got same error... So what resolved the problem and what was the ultimate cause of the problem, there was to many columns defined in the list and I had to delete several columns to publish the workflow in the test environment. This actually issue translates into the there is a limit in SQL Server on how much data the list can store each type of column takes up so much space read more about it here:
https://technet.microsoft.com/en-us/library/cc262787(v=office.15).aspx#Column
So what I did in production was worked with my client to determine how to break up the list into multiple lists and have relationships between them, thus moving some of the columns and data to another list (Think database/list normalization)... I hope this solution helps someone.
I have installed and configured SharePoint 2010 to run on the same box as the SQL Server its running from in Windows Server 2008 R2. Everything is working fine except the search. I have uploaded several documents and tagged several items (documents, tasks, announcements etc), however whenever I search the site using the defaul search, i get nothing returned no matter what i search on, I simply get "We did not find any results for [search term]". I know there is setup needed if you wish to use "FAST search", but do I have to do anything to get the standard default search to work?
Found the answer on SharePoint.SE:
After installing the system you need to configure your indexing job.
Navigate to CA > Service Applications > Search.
You will see a link to your Content Sources. If you edit that it will give you the opportunity to setup a schedule for both Full and Incremental indexing.
You can kick off a full crawl, once completed you will have results if everything is configured correctly.
It does work for people search too . if you edit this content source you will see sps protocol which is for user profiles .
To make people search to work, in Central Administration > Manage Service Applications, make sure to provide a valid domain\user account as administrator in User Profile Service Application.
To add on to Chensformers answers, the account has to have "Retrieve People Data for Search Crawlers" enabled. They have to have it in the Administrators button, even if the Permissions is set to Full Control! Quite misleading.