Update could not find query about workitemupdater

[BlueBasher]

It's the intersection of the two.
Fyi, see here

[msuarez-rmr]

I am having this same issue. A very simple use case where I've selected "Work Items linked to the Build/Release and a Query".

This is from the logs:
2023-08-14T19:52:09.1179418Z Using Build as WorkItem Source
2023-08-14T19:52:09.7160914Z Using Query as WorkItem Source
2023-08-14T19:52:09.8418652Z ##[warning]Could not find query d2ebb6e2-6b1b-4da6-8b38-fb53e8c86146

The query resides in a subfolder of Shared Queries.

What I was testing to see was whether the result of what got updated was the intersection of the two queries (which is what I was hoping) or the superset of the two queries (which would not be helpful to me).

But instead, I wasn't able to get any recognition of the query at all...

[andremusiol]

same issue for me:

the id fetched is correct, but the query could not be found?

[jenishcpatel]

Hello
Enable this both settings from Project Settings and try. it's work for me.

[andremusiol]

Hi there, thank you for the idea! 🙂
But these two options were turned on to begin with when the error/bug was produced:

[BlueBasher]

You need to make sure that the principal that is executing the build (usually the Build Service account), has read permissions on the query.

[andremusiol]

Thank you for your reply BlueBasher
I think it already has(?)

[msuarez-rmr]

@BlueBasher - Can you answer whether "Work Items linked to the Build/Release and a Query" behaves by taking the work items associated with the build/release combined with the work items from the query (aka the union of them), OR if it behaves by taking only those work items that are individually are linked to the build release and part of the query (aka the intersection).

For example, suppose the following:
Work Items Associated with the Build/Release: 1001, 1002, 1003, 1004, 1005
Work Items resulting from the Query: 1004, 1005, 1006, 1007, 1008

Will the work items considered by the "Work Items linked to the Build/Release and a Query" option produce:
Union: 1001, 1002, 1003, 1004, 1005, 1006, 1007, 1008
-OR-
Intersection: 1004, 1005

Thanks!

[msuarez-rmr]

It's the intersection of the two. Fyi, see here

Perfect. I can't think of a good use case for it to be the union, but I certainly have a use for the intersection, so I was hoping that would be the case.

[andremusiol]

Thank you very much for your quick reply!
I gave the shared query permissions another look and added this entry:

Now the extension can access the query and works just fine.
So your first tip did the trick, thank you very much for taking the time and helping me out!

PS
and apologies for posting this as an issue; this one's on me
only a small suggestion: maybe you can include some hint in the warning text being thrown, when the query could not be found? for future users who might be as dense as me 😅