nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Filter issue - id, topic by username and status

Saravana Kumar5

I am trying to figure out the rest api to get the JIRA issues assigned to a user X with status TO DO, and it must return the JIRA id, issue topic, issue status and ignore all other information like comments, issues, description etc.

api i am looking for i assume it must be like this,

curl -X GET -u saravana:xyz http://xyz.yza.local/rest/api/2/search?user=saravana&status=todo

return value must be,

`[ { "id" : "123", "issue" : "JIRA rest api, fetch the user specific issue", "status" : "TO DO"}........more issues]`

Accepted answers

Nic Brough -Adaptavist-

You're not far off, try

curl -D- -u saravana:xyz -X GET -H "Content-Type: application/json" http://xyz.yza.local/rest/api/2/search?jql=status=TO+DO

To get just the id, summary and status (not that you need status, because you know it's TO DO already because that's what you're searching for), add

&fields=key,summary,status

All comments

Nic Brough -Adaptavist-

You're not far off, try

curl -D- -u saravana:xyz -X GET -H "Content-Type: application/json" http://xyz.yza.local/rest/api/2/search?jql=status=TO+DO

To get just the id, summary and status (not that you need status, because you know it's TO DO already because that's what you're searching for), add

&fields=key,summary,status

Saravana Kumar5

hi Nic, thanks for your info... i tried adding the user filter, as curl -u saravana:xyz -X GET -H "Content-Type: application/json" http://xyz.yza.local/rest/api/2/search?jql=status=TO+DO&user=saravana.kumar&fields=key,summary,status ............... somehow, &user=saravana.kumar is not having any effect... it fetches all people's issues

Nic Brough -Adaptavist-

Yes, that's correct. You've used the clause "user". Unless you have a custom field called "user", it's nonsense so the API is ignoring it. I suspect you mean reporter, assignee, creator, watcher or collaborator...