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

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 vote

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 Join to answer
Community showcase
Louis De Jaeger
Posted Thursday in Off-topic

Friday fun: your best joke

Hi all Lets make this Friday fun really fun and post one (or more) of your best jokes! The joke can be about an Atlassian product, or just a really fun joke you want to share! I’m not the best j...

175 views 12 3
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot