Is it possible to list issues by all projects within the REST API for YouTrack?

The API documentation for YouTrack 3.0 seems to suggest that the only way you can get a list of issues is by filtering through a specific project. Is this correct?

I want to be able to search for issues that carry a specific tag across all projects - and a list of all "critical" or "major" tickets across all projects. Is there a way I can do this using the REST API for YouTrack?

Many thanks.

5 comments
Comment actions Permalink

Hello Phil,

There is no possibility to get issues from all the projects. But you can specify projects explicitly in the filter like this: "project: projectName1, projectName2 #Resolved". This will return resolved issues from projectName1 and projectName2. This is not documented yet, so use it with care.

0
Comment actions Permalink

Hi Sergey. Thank you for your reply. Is there any chance it might be something that is added in a future version?

The reason behind the request is that we are developing a series of applications and monitors for YouTrack, to assist us in our own development work. As our developers work across multiple projects it is useful to display all tickets, especially those that are critical or major, from all projects.

We also want to display any tickets that carry a specific tag, and this should search across all projects.

For now we will have to try and specifically include each and every project but I would ask and pray that this could be built into the API very soon. I don't want to have to build my own search to iterate through all the projects collecting the output.

Many thanks.

0
Comment actions Permalink

Hi Phil. Sorry for the delay. Here is a corresponding issue: http://youtrack.jetbrains.net/issue/JT-11551. Please vote for it to get it implemented faster.

0
Comment actions Permalink

In YT 2.0 I used:

http://localhost/rest/project/issues

Has this call been deprecated? It seems to still work in YT 3.0.4.

0
Comment actions Permalink

Yes, it is deprecated. We removed it from docs but left for backward compatibility.

0

Please sign in to leave a comment.