The Issue Checker should have unit tests. At least the Issue.getTickets() methods, but there might be other parts that could be tested as well.
Since the Issue classes are coupled with EJBs, I guess that the best way is through mock testing.
Currently there are only two Issue classes, EccWithKeyEncipherment and NotInProduction mode, and I guess that it doesn't make much sense to test the latter (the functionality is also indirectly tested by developers). So the 4 hour estimate is for a test of EccWithKeyEncipherment ony.