The way GreenHopper works is it goes through quite a few hoops to retrieve the issue status change history. The data is read from Lucene (the classes that interact with the indexes that are created on disk) and it manually matches the incoming and outgoing transition changes to build the status change history. This is done to keep the performance of GreenHopper at an acceptable level.
GreenHopper doesn't expect transitions to happen at the same time and the fast transition functionality within Script Runner is causing change history timestamps to be identical which is breaking GreenHopper. Consequently issues are not appearing on boards when they should be.
Execute the below SQL to identify problematic issues:
If it returns issues that are missing from the boards, it is highly likely this is what is causing problems with GreenHopper.
The fast transition functionality causes GreenHopper issues to not appear, so will need to be disabled for the projects that GreenHopper uses. After doing so a SQL update can be executed to fix the change history records on the affected issues.
Backup the database with native DB tools or use an XML backup prior to stopping it.
Execute the following SQL:
ℹ️ This is for MySQL and will need modifying depending upon the DBMS JIRA uses.
Start JIRA and index it.
Verify the issue is in the chart by accessing it.