Ensures tests are ignored if the currently running JIRA is on an newer build number than when the test was written,
and the tested product/feature has changed after this build.
Why not just remove that test; why is this necessary?
During a Zero Downtime Upgrade (ZDU), a JIRA cluster passes through a state where the binaries are on 'latest',
but the Upgrade Tasks haven't been run yet, hence the database is on 'old'.
In this situation, we want to ensure 'old' behaviour still works properly from a 'new' binary.
Use the @BeforeBuild annotation on existing tests that test 'old' behaviour.
Have a look at its counterpart
SinceBuildRule