The Development field information is not searchable when connecting a repository with a lot of issue keys

Summary

The information about pull requests, commits, etc. that is present in the development panel is not shown in the search results list view when connecting a repository already having a lot of issue keys to sync.

Because of this change of behaviour, it is not possible to run the below advanced searches and to know which issue has what in the development panel:

development[pullrequests]
development[commits]
development[reviews]
development[builds]

Steps to Reproduce

1. Connect JIRA to a repository (BitBucket or Github) having a lot of issues mentioned in the commits. 
2. Wait for the sync to finish
3. Run a search for all the issue having something in the development panel. E.g.:
   development[pullrequests].all >0 OR development[commits].all > 0 OR development[reviews].all > 0 OR development[builds].failing > 0

Expected Results

A list of issues is returned and by showing the Development column in the search results list view you can see the development status for all of them.

Actual Results

No issues are returned.

However, if you open an issue that you know it has some information in the development panel then the information is retrieved and at the successive search the issue is returned in the results.

This behavior is also described in the below 2 thread on communities:

• https://community.atlassian.com/t5/JIRA-questions/JQL-quot-issue-property-development-commits-gt-0-quot-not/qaq-p/298377
• https://community.atlassian.com/t5/Answers-Developer-Questions/Get-commits-info-of-a-JIRA-issue-using-REST-API/qaq-p/530323

In certain cases, changes in Stash will not be updated in JIRA unless you manually view the issue or view it as part of release hub https://confluence.atlassian.com/display/JIRA/Checking+the+progress+of+a+version.
These cases are:

• When JIRA is down or unreachable
• When a repository is pushed to Stash with a lot of issues mentioned in the commits

Notes

Because of JSWCLOUD-16143 the development info may be missing from the search results even after applying the workaround (the issues having development related infos are now found by the search, but the field shows as empty in the list view).

Workaround

You can ask support to provide a list of all the issueIds for your instance and then run a script that calls the below endpoint for each issueID:

• https://INSTANCE/rest/dev-status/1.0/issue/summary?issueId=ISSUE-ID

E.g.

#!/bin/bash
while read line
 do 

curl -u <e-mail>:<api_token> -H "Accept: application/json" -H "Content-Type: application/json" -X GET "https://<INSTANCE_URL>/rest/dev-status/1.0/issue/summary?issueId=$line"

echo -e "\n"

sleep .5

done < file_with_issues_ids.txt