List Work Itens across projects

[abrito92]

First of all, great job in this extension, it's an incredible usefull piece.

So, i've trying to figure this one out (even searched high and low here on the repo) and so far no luck.

I am using the newest version of the cross platform extension for my azure pipeline and i am trying to get the Work Itens in my release notes.

However no matter what i do, i cannot make it list them. For context, our company utilizes a project just to center the teams boards and tasks, therefore every pipeline is outside that scope.

So, my question is: is it possible to get the workitens from other projects using this extension?
I've tried to utilize wiqlWhereClause pointing to a different System.TeamProject with no luck. It seems no matter what way i try, it searches the WI inside the project where the pipeline is beeing run.

[rfennell]

The task should find any WI that are associated with commits/changeset. If you developers are not doing this then nothing will be found, so not listed. Could this be the issue?

If that is the case then wiqlWhereClause option may help as this can be any WIQL with or without a project filter in the clause, but saved as a 'wiqlSharedQueryName maybe be a better option as you can just use a Shared query to get the WI.

The WIQL based solution are not as good IMHO as proper associated WI, but for some people it is the only option

[pak-sergey]

I have this:

[rfennell]

A few ideas

• Is this a generic Git repo (published as a WIKI) or the dedicated auto created WIKI repo ? If the latter set the permission on that directly, as I am not sure Azure DevOps applies the 'all repos' permissions to it
• When having an issue like this I would also try applying permissions directly to the target repo
• If this still fails, run the task with a PAT to run as a named user, just to work up from a point where something is working

[rfennell]

Oh, and there is a unit test you can repurpose to test the the access locally

[pak-sergey]

The problem is not only with the WIKI, I have another pipeline, where I didn't applied yet Release Notes with wiki, but it has the task to put Tag number and git-push fails too.
It's caused by disabling:
Limit job authorization scope to current project for non-release pipelines
Limit job authorization scope to current project for release pipelines

[pak-sergey]

I found it, the permissions for Project Collection Build Service also needs to be changed.