Hi,
I have Sucessfully configured Team foundation server for Bug Tracking in Test studio . when i try to submit a bug I get the following error "Unable to submit bug to Team foundation Server .Error:Symptom has an invalid value NULL" Attached is the trace log
this was working perfectly in 2012 Version I cannot perform this after updgrading to 2013 Vesion. Need Help on this error
Thanks
I have Sucessfully configured Team foundation server for Bug Tracking in Test studio . when i try to submit a bug I get the following error "Unable to submit bug to Team foundation Server .Error:Symptom has an invalid value NULL" Attached is the trace log
this was working perfectly in 2012 Version I cannot perform this after updgrading to 2013 Vesion. Need Help on this error
Thanks
9 Answers, 1 is accepted
0
Hello Raghavan,
Boyan Boev
Telerik
Thank you for contacting us.
In which 2012 version it was working perfectly? As of version 2012.2.920 and later you should create the file TFSMappings.xml in the following folder which you should have:
C:\Program Files (x86)\Telerik\Test Studio\Bin\Plugins
The folder BugTrackers existed in versions prior to 2012.2.920.
Please check out this article.
Let me know if this helps.
Boyan Boev
Telerik
0
Raghavan
Top achievements
Rank 1
answered on 13 Nov 2013, 11:34 AM
I am not sure on the version number.
I will follow the steps based on the link you have provided to fix and let you know
Thanks
0
Hello Raghavan,
Boyan Boev
Telerik
Please take your time and update this thread accordingly.
Thank you!
Boyan Boev
Telerik
0
Deeb
Top achievements
Rank 1
answered on 24 Jun 2014, 07:17 PM
Hello Boyan,
I have exactly the same issue.
The solutions of TFSMappings.xml allows the New Bug to be saved, but TFS "Symptom" field now holds the exact literal in <FieldValue> tag.
Is there a way to store the "Description" value generated from Test Studio instead?
Also, what is the default location that holds Test Studio Bug "Description" when mapped to TFS Bug?
I have exactly the same issue.
The solutions of TFSMappings.xml allows the New Bug to be saved, but TFS "Symptom" field now holds the exact literal in <FieldValue> tag.
Is there a way to store the "Description" value generated from Test Studio instead?
Also, what is the default location that holds Test Studio Bug "Description" when mapped to TFS Bug?
0
Hello Mohamed,
I am not sure if I understand you correctly.
Please give us some more detailed information about your scenario.
Please check out also this article which describes TFSMappings.xml.
Hope to hear from you soon.
Regards,
Boyan Boev
Telerik
I am not sure if I understand you correctly.
Please give us some more detailed information about your scenario.
Please check out also this article which describes TFSMappings.xml.
Hope to hear from you soon.
Regards,
Boyan Boev
Telerik
0
Deeb
Top achievements
Rank 1
answered on 26 Jun 2014, 10:16 AM
Hello Boyan,
My problem is that if I follow the exact steps in the article, I would store the static text "NewName" in BugTrackingName field.
Is there a possibility to store the value of a field from Team Studio instead, like "@Description" for example.
My problem is that if I follow the exact steps in the article, I would store the static text "NewName" in BugTrackingName field.
Is there a possibility to store the value of a field from Team Studio instead, like "@Description" for example.
0
Hi Mohamed,
Unfortunately you cannot copy from one field to another.
You should type the value directly into the TFS field.
Let me know if I am missing something.
Regards,
Boyan Boev
Telerik
Unfortunately you cannot copy from one field to another.
You should type the value directly into the TFS field.
Let me know if I am missing something.
Regards,
Boyan Boev
Telerik
0
TankTheFeels
Top achievements
Rank 1
answered on 19 Jan 2016, 07:57 PM
I followed your guide, but I'm getting the same error as Deeb. Unable to submit bug to Team Foundation Server. Error: Symptom has an invalid value of NULL.
0
Hello Matias,
Please elaborate a bit more on your scenario so we can assist you best.
1. How exactly you are submitting the bug? Do you have something specific?
2. Please send us the application log. Clear it first and reproduce the issue.
Hope to hear from you soon.
Regards,
Boyan Boev
Telerik
Please elaborate a bit more on your scenario so we can assist you best.
1. How exactly you are submitting the bug? Do you have something specific?
2. Please send us the application log. Clear it first and reproduce the issue.
Hope to hear from you soon.
Regards,
Boyan Boev
Telerik