Justus, I haven't done any checking nor know of anything specific thing missing. There are very few linked issues to this one, so it was not clear what has been covered elsewhere.

Matt, I agree. As I said I did check (twice! like Santa). But I'm only human and sometimes mistakes happen .

Justus,

I feel that the onus is on you as the closer to make sure that all the issues have been raised elsewhere. There's no way you're going to get every commenter to go back and check that their concern has been logged in another issue.

It's one of the problems with having a single issue for feedback, which avoids duplicating information, versus having lots of feedback issues.

Best wishes,

~Matt

Bob, I believe that is the case. I just did another quick scan back and didn't see anything that hasn't been raised elsewhere. If there's anything you're especially concerned about (or know that I've missed) can you either raise an issue or let me know?

I agree, however, I would also expect you to open issues for any feedback documented here that has not been addressed with the current implementation or other issues.

I think this issue has served its purpose over the past two years and has now reached a point of no longer being as useful as it could be. We want continuing feedback but a single humongous, never-ending issue on a bewildering variety of topics no longer presents a good way for that to happen.

http://answers.atlassian.com is a good resource for questions while http://jira.atlassian.com will continue to be the place for feature requests and bug reports.

ltflorao,

You can see the API docs for each version by going to http://docs.atlassian.com/jira/REST/

Guys,

Will be great if every release of REST API would be accompanied by Release Notes. We only found the documentation for REST Plugin, and it's outdated.

Cheers,
Lucas Timm

Not really, as you propose to retrieve data for all issues from the result. If you like to do something like the issue statistics like in the Issues tab and have a JQL query with 1000 issues result size this would be a hudge request.

I know, there is nothing like a "select distinct" in JQL. But Lucene can return such meta data for a result set. Question is, if this is configured and reachable through Java or REST API. I guess JIRA Charting plugin is doing similar for its pie charts for assignee or project.

Kind regards
Holger

holger@schimanski-web.de: As you noted, you can request the project for each issue in the search results by adding fields=project (in fact, project is returned by default anyway).

Alternatively, you can exclude project, and just request (say) summary with fields=summary. This also gives you key and id. Real example: https://jira.atlassian.com/rest/api/2/search?jql=assignee%3Dmquail&fields=summary

You then have two choices for getting further details (for example, the project):

1. You could fetch each individual issue and inspect it's project, e.g. https://jira.atlassian.com/rest/api/2/issue/107338?fields=project
2. You could do a bulk-fetch using JQL's IN clause, e.g. https://jira.atlassian.com/rest/api/2/search?jql=id%20in%20(163184,%20162886,%20162862,%20162584)&fields=project

Does that answer your question?