Reported by Michl Steglich Mar 15, 2017 at 01:28 PM tfs
When you create a taskgroup -> add default values for task group variables -> save -> add a variable to task group -> use taskgroup with default values, then you will face the problem that the values will be empty. In my case, I used the task execute a command line command with the values as parameters.
TFS2017U1
Hi,
Can you elaborate the flow so that we can try to repro the issue.
How many variables have you added to the Task group.
Have you provided default values for all the variables in Taskgroup. Can you share an image.
When you add the taskgroup to the release definition, were all the default values for all the variables empty?
Please share the snapshots at rm_customerqueries at Microsoft dot com.
Thank you for your feedback! In order for us to investigate this further, Can you elaborate the flow so that we can try to repro the issue. Can you share some snapshot images. We look forward to hearing from you!
Thank you for your feedback! Unfortunately, right now we don't have enough information to investigate this issue and find a solution. If this is still an issue for you, please update to our latest version. If you are still able to repro it, please provide us with more info! Thank you for helping us build a better Visual Studio!
Also raised here, and due to be fixed soon: https://developercommunity.visualstudio.com/content/problem/183125/taskgroup-parameters-ignored-if-default-value-used.html
Team Explorer VS2013 TFS 2010 - TF30063
0
Solution
TFS 15 Changeset incorrectly associated to tasks automatically
2
Solution
TF30063 when changing Notification URL
2
Solution
Useful to allow tasks to be 'unassigned'
0
Solution
Cannot add TFS server group to Access Level
1
Solution
Build definition content not appearing in browser-based log
4
Solution
TFS10158 error when using shelveset picker to queue new build
2
Solution
unable to see build step logs, tfs 2017
2
Solution
TFS 2017, Users at Stakeholder access level doesn't have search box
3
Solution
Discussion work item lookup using # fails in project with custom process template
0
Solution