api/2/search doesn't return issues after сertain date

Igor Vasilyev June 18, 2017

I use api/2/search with next parameters

 

{"jql":"worklogDate >= \"2017-06-13\" AND worklogDate <= \"2017-06-15\" AND worklogAuthor = SOME_USER","startAt":0,"maxResults":1000,"fields":["project","issuetype","components","summary","worklog"]}

 

(SOME_USER - replaced to certain user)

but response doesn't contain issues after 13.06.2017.  

Jira was updated 14.06.2017.  Request doesn't work correctly after update

Can you please advise?

1 answer

0 votes
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 19, 2017

I would try to force JIRA to do a 'lock JIRA and reindex' to see if this helps.  Everytime JIRA upgrades there is an expectation that a reindex has to occur. 

If the indexes in JIRA might have become corrupted, the issues could still be there, but might not be searchable until the indexes are fixed.   If they are corrupted, then doing a lock and reindex forces JIRA to rebuild the indexes.  I would recommend waiting to do this at a time when you can afford to have JIRA be down.  This process can take some time and users will not be able to use JIRA until this is complete.

Suggest an answer

Log in or Sign up to answer