Replies: 2 comments
-
The WI returned by WIQL are placed in a special array (to avoid confusion with the primary ones associated automatically by the Azure DevOps API). To access them use the follow handlebars
|
Beta Was this translation helpful? Give feedback.
-
Thank you! I think I had access issues, that I managed to get through. Now I have a template with the Workitems. One other question is regarding the test harness. I think there are also issues for accessing the Items (WIQL and WI in general)
Output: List of User Stories in this Release (0)List of Tasks in this Release (0)List of Commits for this Release-> This part works. All commits are listed My settings:
This is how the handlebar template looks like now (I dont need to use the WIQL here anymore):
|
Beta Was this translation helpful? Give feedback.
-
Hello!
Sorry I am a bit new to handlebar templates and also azure pipeline.
I am trying to figure out how to get workitems inside of my template.
This is a snippet of my template:
`
XXX API TITLE
Release Notes for {{buildDetails.buildNumber}}RSION
These are the most updated Workitems
Total Number of Work Items: {{workItems.length}}
`
It returns 0 which is not true.
Here is a piece of my logs inside the pipeline:
Loading template file /opt/vsts_agent/_work/1/s/xxxxxx.md
##[debug]Loading handlebar template
##[debug]Processing template
##[debug] WI: 0
##[debug] CS: 1
##[debug] PR: 0
##[debug] Builds: 0
##[debug] Manual Tests: 0
##[debug] Manual TestConfigurations: 0
##[debug] Release Tests: 0
##[debug] Related WI: 0
##[debug] Related Tests: 0
##[debug] Indirect PR: 0
##[debug] Consumed Artifacts: 0
##[debug] Published Artifacts: 0
##[debug] Query WI: 13
##[debug]Processing handlebar template
Loading handlebars-helpers extension
Here is my Task Setup
I had to add XXX for a few sensitive Information, but I made sure the paths were correct.
Beta Was this translation helpful? Give feedback.
All reactions