Existing Handlebar template doesn't work all of a sudden

[christianepcruz]

Hi - i just noticed that my existing handlebar templates are not working anymore. Can you please help and see if there are things I need to update for it to work again? The goal would be just to get the associated work items but only User Stories and Bugs and put it into a 2 different tables.

Here's my existing template:

        inlinetemplate: |
          # Release Notes for Build 
          **Build Number**: {{buildDetails.id}}

          ***List of Userstories***

          | ID | Title |
          |-|-|
          {{#forEach workItems}}
            {{#if (eq (lookup this.fields 'System.WorkItemType') 'User Story')}}
            | {{this.id}} | {{lookup this.fields 'System.Title'}} | 
            {{/if}}
          {{/forEach}}
          
          ***List of Bugs***
          
          | ID | Title |
          |-|-|
          {{#forEach workItems}}
            {{#if (and (eq (lookup this.fields 'System.WorkItemType') 'Bug') (or (eq (lookup this.fields 'Microsoft.VSTS.Common.Severity') '1 - High') (eq (lookup this.fields 'Microsoft.VSTS.Common.Severity') '2 - Critical') (eq (lookup this.fields 'Microsoft.VSTS.Common.Severity') '3 - Medium')))}}
            | {{this.id}} | {{lookup this.fields 'System.Title'}} | 
            {{/if}}
          {{/forEach}}

[rfennell]

My release notes task has not been updated since November 24, so if your template worked after this date we can rule out a change in the task

So, an you provide more context?

• When did it stop working?
• Have you edited your AZDO process template?

[christianepcruz]

Hi @rfennell appreciate the quick response. I just thought of this last night also, but I think it started not to work when we used a different project for our Work Items (User stories and Bugs).

So my quick question would be, is it possible for the task to work the same way even tho the builds, repos (Project 1) and the workitems (Project 2) are in a 2 separate projects but still within the same organization.

[rfennell]

My task just returns the WI and CS associated with the a pipeline run via the Microsoft API, so if this API returns cross project it should work.

The only difference from this is for PRs, these have 'bespoke' logic, to enable ross project search here you need to enable the searchCrossProjectForPRs =true parameter - but this must be done with care as it makes the task very slow to run