Home Dashboard Directory Help
Search

Export Query Results to Excel Missing in TFS 2010 TSWA by arwebb4


Status: 

Closed
 as By Design Help for as By Design


1
0
Sign in
to vote
Type: Bug
ID: 694566
Opened: 10/12/2011 12:57:16 PM
Access Restriction: Public
Moderator Decision: Sent to Engineering Team for consideration
0
Workaround(s)
view
3
User(s) can reproduce this bug

Description

Recently upgraded to TFS2010 and was unpleasantly confronted by several users they can not longer Export TSWA queries to excel. I have a lot of unhappy users.
Details
Sign in to post a comment.
Posted by shnigganoo on 7/11/2012 at 3:54 AM
Can someone from the Web Access team please provide an update or proper solution to this issue. This is by far the biggest gripe our TFS Web Access users have, that along with the fact that you cannot scroll the reports window that was also raised along with this issue as a bug here: http://connect.microsoft.com/VisualStudio/feedback/details/582411/team-system-web-access-view-as-a-report

This should never have been closed. It's a huge leap backwards and our users are wondering if the hassle we went through to migrate to TFS 2010 was really worth it!
Posted by arwebb4 on 10/13/2011 at 9:08 AM
Not to sound ungrateful for the feedback, but did anyone read the issue? I'm not trying to export a single WI to excel, we need to be able to export our TFS query results to excel. The resolution provided below has no value at all. Doesn't even work for a single work item.
Posted by Microsoft on 10/13/2011 at 8:16 AM
Thank you for the feedback. Sorry for the inconvenience. Copy-to-clipboard support was added in TFS 2010 Web Access. So the following workaround is available:

1. Select the work items to export (Ctrl-A to select all)
2. Press Ctrl-C to copy to clipboard
3. Open Excel (or any text editor)
4. Press Ctrl-V (or click the Paste menu option)
Posted by MS-Moderator08 [Feedback Moderator] on 10/12/2011 at 11:58 PM
Thank you for submitting feedback on Visual Studio 2010 and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by MS-Moderator01 on 10/12/2011 at 1:44 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.