nFeed 5.5: JQL querying in JIRA database - Valiantys - Atlassian Platinum Partner

nFeed 5.5: JQL querying in JIRA database

Querying in JIRA made easy

nFeed version 5.5 is now available on the Atlasssian Marketplace.

The newly-released nFeed 5.5 includes the ability to query the local JIRA database with the native JIRA Querying Language (JQL). The new feature makes querying a list of issues easier, especially for users who are not aware of the JIRA database structure. Let’s take a look at this through a simple example.

Formerly with SQL

Let’s imagine that we need to set a select list which retrieves all JIRA issue keys whose priority value is set to Major. In the JIRA database, the issue key cannot be retrieved simply from one table, but has to be built from the two tables jiraissue and project. In addition, the jiraissue table only stores the corresponding priority ID and not its label. The priority label is actually stored in the priority table. With that said, one corresponding SQL query is:

SELECT CONCAT(project.pkey,'-',jiraissue.issuenum)
FROM jiraissue, project, priority
WHERE = jiraissue.project
AND = jiraissue.priority
AND priority.pname = 'Major'

This is not so easy for an apparently simple initial query. As you can see, the user needs to have a clear idea of the JIRA database structure (tables and attributes) in order to build a working query. The whole nFeed field configuration will then be:


The template field is set to {0} in order to retrieve the first attribute of the query result.

Now with JQL

The same scenario can be set way more easily with the new JQL query feature. In the nFeed field configuration panel, next to the JIRA datasource, you will notice a switch between SQL and JQL:


The user just needs to click on the JQL button in order to build a JQL configuration for the nFeed field. The previous scenario can be translated in this simple and intuitive JQL query:

priority = Major

And that’s it – an easy way to build issue lists. The entire nFeed field configuration will then look like this:


Note the difference between SQL and JQL when it comes to Template. The JQL querying tool uses a convenient way to set the template by only selecting the issue attribute between brackets. The list of accessible attributes is available in the link below the Template field – Available variables.

Give it a go

This article only describes one process to achieve a simple JQL query. As with the SQL querying tool, JQL allows the use of Velocity variables in order to build more dynamic nFeed fields. The best news? our latest version of nFeed is now available on the Atlasssian marketplace.

Cutted Triangle

Subscribe to the Valiantys Newsletter

Registered request ! Subscribing... This is not an email An error occured

In accordance with our privacy policy, we are committed to respecting your personal data.

Contact us

Our Atlassian certified consultants will be happy to answer you.

Join us

We're building the next dream team - Are you in?

Follow us

We use cookies for the operation of our website. This is to improve its use, to personalize your experience, and to compile visitor statistics. By continuing to use this site, you consent to this policy. You can manage the settings and choose whether or not to accept certain cookies whilst browsing. For more information, see our privacy policy. Our privacy policy

Privacy settings

In order to facilitate your navigation and to provide you with the best possible service, we use cookies to improve the site to the needs of our visitors, particularly according to the number of visitors. For more information, please read our privacy policy. Our privacy policy


Google reCAPTCHA is a system designed to distinguish humans from computers, so that bots are unable to maliciously fill out forms on behalf of a human being.


Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels. Used by the social sharing platform AddThis to store the user's usage history of the AddThis sharing widget. Registers a unique ID that is used to generate statistical data on how the visitor uses the website.


Targeting Cookies: Targeting cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant advertising on other sites. They are based on uniquely identifying your browser and internet device. You can turn off the use of cookies for targeted advertising here. When the button is green, targeted cookies are on. When the button is red, targeting cookies have been turned off.

Social Media Cookies: These cookies are set by a range of social media services that we have added to the site to enable you to share our content with your friends and networks. They are capable of tracking your browser across other sites and building up a profile of your interests. This may impact the content and messages you see on other websites you visit. If you do not allow these cookies you may not be able to use or see these sharing tools.