Jira will not index existing dev related information created prior to the app link setup against the JQL search

Issue Summary

JQL offers the ability to use the number of commits/PRs an issue has as criteria for advanced searches. See the example below

development[commits].all > 1

• Issues that contain more than 1 commit

Currently Jira is only able to index the development field taking only new commits and PRs that were created after the application link has been setup (e.g. app link with Bitbucket Server), or when you open issues that contain such information.

That behaviour causes inconsistencies in the results. For example:

• Issues that have commits will be returned when searching for development[commits].all = 0
• Once you open that issue and load the development panel Jira will index it correctly though. That issue will not be displayed in the results anymore (of the query used as example)

The same behaviour happens to migration from Server to Cloud.

Steps to Reproduce

• Have a Jira Server instance linked with BB Server trough app link
• Make sure there are issues that contain commits
• Migrate from Server to Cloud in a way that such data is also migrated
• Set up an application link from the Jira Cloud instance to BB Server
• Perform the following search:

  development[commits].all = 0
  

Expected Results

The issues that contain commits will not be returned by that query.

Actual Results

Those issues will still be displayed in the results until you open then and load the dev panel information. Jira will then index those information correctly.

Workaround

None at the moment.