Unlock the Power of JQL Filters in Released Roadmaps

If you are a frequent user of Jira, you are likely familiar with filters to narrow down the large list of Jira issues to just the items you care about.

Released works the same way. To narrow down the issues for your release notes or roadmaps, you can use filters in Released. And just like Jira, Released supports JQL (Jira Query Language).

JQL opens up a myriad of possibilities for better managing and visualizing your Jira issues. Let's dive into how you can leverage JQL with a powerful example.

What Can You Do with JQL Filters?

Imagine you want to display all issues that are:

• Planned

• In Progress

• Done (but limit the “Done” column to issues completed in the last 30 days)

JQL makes this task incredibly straightforward!

A Quick Demo

Here’s how you can achieve this:

statusCategory != Done OR (statusCategory = Done AND updatedDate >= endOfDay(-30d))

Breaking Down the JQL Query

This JQL query does the following:

1. statusCategory != Done: This part of the query fetches all issues that are not in the "Done" status category.

2. (statusCategory = Done AND updatedDate >= endOfDay(-30d)): This part of the query fetches issues that are in the "Done" status category but have been updated within the last 30 days.

The combination of these two conditions ensures that you get all issues that are either not done or done within the last 30 days. This is incredibly useful for keeping your roadmap relevant and up-to-date without showing outdated completed tasks.

Why Use JQL Filters?

Using JQL filters allows you to customize your roadmap views in ways that standard filters can't match. You can create highly specific queries to drill down into the exact data you need. This power and flexibility make JQL an invaluable tool for any project manager or team lead.

Additional Tip: Use "resolutionDate"

While the updatedDate field is useful, a more accurate field to use would be resolutionDate. Unfortunately, Jira Product Discovery (JPD) doesn’t set the resolution field by default. However, if you can ensure that the resolution date is set for your issues, you can refine your queries even further.

For example:

statusCategory != Done OR (statusCategory = Done AND resolutionDate >= endOfDay(-30d))

This would provide even more precise filtering based on when an issue was resolved, rather than just when it was last updated.

Conclusion

JQL support in Released Roadmaps is extremely powerful. It provides the flexibility and precision needed to control what details to share with stakeholders or customers. Whether you want to filter issues based on status, update date, or any other criteria, JQL makes it easy.

Try out these JQL filters today and see how they can transform the way you manage your projects!

By incorporating these JQL filters into your workflow, you can ensure that your roadmaps are not only accurate but also tailored to your specific needs. Happy filtering!