Search

Team Foundation Service Bug - Sprint name issue (Invalid characters , 404 NOT FOUND) by Frode Fuglestad

Closed
as Duplicate Help for as Duplicate

3
0
Sign in
 to vote
Type: Bug
ID: 779485
Opened: 2/19/2013 12:40:05 AM
Access Restriction: Public
1
Workaround(s)
3
User(s) can reproduce this bug
Invalid url / rendering of sprint title. Unsupported characters not being validated?

The url path for the iteration is:

/DefaultCollection/Noreco%20Intranet/_backlogs/Iteration/Release%201/Sprint%203%20-%20Wow%20%2B%20Speed%20%3D%20Inside%20Noreco
Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Team Foundation Server 2012

Steps to reproduce

I changed the name on one of our sprint iterations, by clicking on the sprint name and "set dates".

Name for the iteration was set to be "Sprint 3 - Wow + Speed = Inside Noreco" and hit save & close.

Next i clicked on the sprint again to verify the name change. Here the problem appeared, the url that is generated for this sprint title is not valid / rendered correctly and page results in 404 not found.

Product Language

English

Operating System

Windows Server 2008 R2 SP1

Operating System Language

English

Actual results

Invalid url / rendering of sprint title. 404 NOT FOUND!

I am not able to change back the sprint title/name to a valid one!

Expected results

Sprint should be displayed with the backlog items as all other sprints/iterations does.

Again, this is not for Team Foundation Server 2012, this is for Team Foundation Service at visualstudio.com. I could not find a proper bug reporting site for this product!
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 2/20/2013 at 10:39 AM
Thanks, this bug is already on our list to fix. The issue is that we do not handle the '+' sign well. If you replace the '+' in the iteration it should start working.
Posted by Microsoft on 2/20/2013 at 4:18 AM
Thanks for your quick response. We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Frode Fuglestad on 2/20/2013 at 12:59 AM
I have already provided all the information you need to reproduce the bug. And i found a workaround myself to pass the issue that it generated. So please do the reproducing yourselves with the tools you prefer to document with.

Thanks!

Frode
Posted by Microsoft on 2/19/2013 at 11:04 PM
Thanks for your feedback. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please use Microsoft Visual Studio 2012 Feedback Tool to collect steps while you're repro'ing the issue?

Visual Studio now has an extension called Microsoft Visual Studio 2012 Feedback Tool, available on the VS gallery(http://visualstudiogallery.msdn.microsoft.com/f8a5aac8-0418-4f88-9d34-bdbe2c4cfe72).

The extension allows you to
1. upload files,
2. collect trace and dump files
3. collect steps while you're repro'ing the issue, as well as
4. SQM logs about VS extensions installed
5. System details (in DxDiag output)

Please submit this information to us within 4 business days. We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 2/19/2013 at 12:50 AM
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.
Posted by Frode Fuglestad on 2/19/2013 at 2:06 AM
I found a workaround to fix the broken or failing rendering of the url.

Navigate to https://youraccount.visualstudio.com/DefaultCollection/Project name/_admin/_iterations

Here you will see a list of all iterations, right click the failing sprint and select open. I guess this one opens by ID, and you can sucessfully change the title to use supported characters and a new valid url will be generated!
© 2013 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement