Quick Intro

You will be glad to hear that we've been hard at work on JQL Issue Select for Jira. The new version is now ready with unmatched features and major performance improvements.


For those who don't know the app, let's make a quick introduction.

JQL Issue Select for Jira, or JIS for short, is a Jira app that introduces SelectList like custom field types to your Jira system. Instead of making the user select an option from a predefined set of options, these custom fields display the results of a JQL query as options and let the user pick from those options.


The advantage here is obvious. SelectList fields contain a static list of options and to make change on this list, you have to go to the Jira admin everytime. When you manage these items as Jira issues, you can set permission for who can create/update/delete those Jira issues and you don't have to go to the admin everytime.


The possibilities are endless but let's name a few:

For example:

  • You can create a Jira project named Customer Management with issues of type Customer in it and associate the Proposal issues in your CRM project to those customers using a JIS field.
  • You can create a Jira project named Asset Management with issue of type Asset in it and associate your service desk tickets with your assets using a JIS field.
  • You can create a Jira project name Product Management with issue of type Product in it and associate your tasks with your products using a JIS field.
  • etc. etc.


With JIS 2.0, major new features and improvements take stage.


New Field Types

JIS v2.0 introduces JQL Advanced Select and JQL Lookup Field types:

JQL Advanced Select

JQL Advanced Select is designed to replace old (and now deprecated) field types from JIS v1.x.

Just like the old fields, you set the JQL to define the pick list of the field and the View Pattern to define how the issue in the pick list will be rendered.

The new JQL Advanced Select type can be set to work as a Dropdown for single-select and as a Label field for multi-select.



We also improved how the field works on user's screen. The new field does paging and supports infinite scroll in the pick list. It also lets the user search among options.




Performance

All these client-side improvements combined with countless optimizations implemented in the background make it capable of working with pick lists that have thousands of issues. The performance improvement is stunning.

Jira Issue Search

JQL Advanced Select field comes with two indexers which enable you to select whether the field will be indexed using keys of selected issues or the display text of the selected issues. This makes it possible to search the field using issue keys or display values.


JQL Lookup Field

JQL Lookup Field is another new field type that can be used to bring read-only information from other issues.

It works in perfect harmony with JQL Advanced Select. For example you can configure a JQL Advanced Select field to let the user select a customer and then configure a JQL Lookup Field to display the contact information of the selected customer.



Migration

Deprecated field types are included in the app for backward compatibility but we also built a migration screen to move field values easily from fields of deprecated field types to fields of new JQL Advanced Select field type.


Dynamic JQL with New Token System

The dynamic token system of JQL Issue Select is a major area of improvement as well.

The new token system can not only use issue fields in your JQL, can also use Jira project information (like key, name, versions, components etc.) and current user information (like, username, email and user properties). It can also use field values from parent issues or other issues selected in JQL Advanced Select fields.

You can define a JQL like "project = {project.key} and assignee = {issue.cf_12345.assignee}" which will result in a pick list that shows all the issues in the current project that are assigned to the assignee of the issue selected in JQL Advanced Select custom field with ID 12345. You can even use other issue references in a chain, something like "assignee = {issue.cf_12345.cf_98765.assignee}"

For detailed information you can consult the documentation: JIS v2.0 - Dynamic Patterns

Jira Service Desk Customer Portal Support

The new JQL Advanced Field supports Jira Service Desk Custom Portal with all search, paging and infinite scroll capabilities.


There are the improvements that are visible from the surface. With relentless work and rigirous testing, JQL Issue Select is better, faster and more stable than ever.

Try it today. Go to JQL Issue Select page on Atlassian Marketplace.


As always, feel free to reach us through plugin@obss.com.tr or pluginsupport.obss.com.tr if you have any questions.

Emre TOPTANCI