October 13, 2019
Hi there, pals! How is it going?
Sweet Bananas team is really glad to announce that JQL Booster Pack v1.8.0-RELEASE has been shipped and can be download for FREE at Atlassian Marketplace.
Please, before installing this new version, double-check if you have installed any Jira third-party app on your system that already provides JQL functions metioned below.
If so, refers to JQL function clashes with Script Runner and other Jira apps document to learn how to avoid conflics with any existing Jira apps.
This JQL Booster Pack version introduces FOUR new JQL functions, see what is new for this release:
Quarterly Reporting Support
Most financial reporting and dividend payments are done on a quarterly basis. A quarter is a three-month period on a company's financial calendar that acts as a basis for periodic financial reports and the paying of dividends. A quarter refers to one-fourth of a year and is typically expressed as "Q1” for the first quarter, “Q2” for the second quarter, and so forth.
Currently there is no way to dinamically query issues created, updated, due,... on the current quarter (or in the past quarter) but from now you can! Use our two brand new JQL functions startOfQuarter() and endOfQuarter() to retrieve data within an specific quarter period with ease.
Isn't it wonderful? 🤜💥🤛
Improved Issue Relations Search Capabilities
Within the last JQL Booster Pack releases, we had introduced the possibility to query some relationships between issues, (e.g: Parent ⟷ Subtask, or Epic ⟵ Story) but this feature was not complete at all.
Now we are quite happy to announce the inclusion of two new JQL functions related to this feature, issuesInEpics() and linkedIssuesOf() to allow you to query all availables issue relations on your Jira instance.
Epics are a helpful way to organize your work and to create a hierarchy. The idea is to break work down into shippable pieces, so that large projects can actually get done and you can continue to ship value to your customers on a regular basis. Epics help teams break their work down, while continuing to work towards a bigger goal.
An Epic can be broken down into specific tasks (called “stories,” or “user stories”) based on the needs/requests of customers or end users. However, there is no way to query these Epics based on their Stories statuses or fields.
Thanks to the issuesInEpics() function you can from now, query issues within Epics matching a given subfilter. That is, you can retrieve for example all issue within any unresolved Epic of a concrete project.
Issue linking allows you to create an association between two existing issues on either the same or different Jira servers. For example:
- An issue may relate to another.
- An issue may duplicate another.
- An issue may block another.
Any Jira administrator can customize the existing types of link or even create new ones. In addition, it existis some special link types called 'System Links' that cannot be seeing within the UI (e.g. The relationship between a subtask and their parent or the relationship between Epics and Stories).
You can now query all of them (incl. the system ones) by using the linkedIssuesOf() JQL function.
Does all this seems interesting to you? Don't hesitate to give us your feedback.
If you have any comments or suggestions, please feel free to send them directly to us.
Sweet Bananas Team