As a general rule, if your tests are important to you and your team, then Jubula is a good fit. Below is a list of other criteria that may help you to make your decision:
If you want your tests to be automated by testers that are not necessarily developers.
If you expect your software to undergo changes in its lifecycle that will be reflected in the workflows, the business logic and the GUI.
If you want to be able to write tests in parallel with your development, before a version of the application is available (in agile processes, for acceptance test driven development, for quicker feedback, ...).
If you want to use the tests as a basis for collaboration with the whole team and with customers, allowing each group to understand and discuss what a test does.
If you want to involve stakeholders in defining and discussing acceptance criteria that can be provided as automated tests.
If your quality is worth enough to you that you can spend a few hours learning how to use a tool.
If you want your test automation to be a part of the software quality process, so that the process of automation checks the requirements, not just the implementation.
The Jubula team has released the latest official version of Jubula. Version 8.4.0 was released on 19th December 2016 and now allows users to write tests using conditions and loops as well as various other additions to simplify test creation, especially in more complex scenarios.