Skip to end of banner
Go to start of banner

Rationale & How It Works

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Kepler Custom Fields Pro

 

This add-on came out as a necessity in a real large project. The idea of the add-on has been in the back of our minds since we first started to customize JIRA for our clients, however we didn't have the time to implement it, until now.

The Problem

Let's talk about select lists, for instance. When dealing with select lists in JIRA, you have the possibility to create static select lists via the usual custom fields. This is awesome, but not enough. Select lists may be dynamic in nature, in which case the usual custom fields are really not helpful.

Imagine that your field is actually a select from the database. Or a list of components that should be determined at runtime based on user roles in the project.

We tried to solve such several problems in Power Scripts for JIRA (formerly known as JJUPIN) Live Fields by hiding select lists options elements. However, this is usable only for select lists which are known (static), because we could not determine easily at runtime what values have been shown in the UI.

 

Entering the Stage: KCF - Pro

 

KCF-Pro resolves all the above problems of the dynamic select lists, in our own way: data for the CF is obtained through SIL (although we plan to add more options on it); at save time, we allow one more optional interaction with the CF through SIL, enabling you to update dependent fields or issues (or maybe just log it).

 

The data is obtained through a SIL script, allowing you to intervene in the process of data build-up even in the stages of the autocomplete. This is a huge advantage for JIRA-addicts (like we are) because it allows you to filter more efficiently based on what user types in the field (car parts, computer parts, airplane parts, ...)

Selection of the data is scripted, too. This means that you can intercept in SIL the selection the user has made and act on it.

 

Data may be presented to the user as:

  • Select lists (simple or with auto-complete, single or multiple)
  • Radio buttons (if you have only a handful of choices)
  • Checkboxes (for multiple, but few, choices)

To please the eye of the user and to make the lists look like the JIRA standard lists, we added special renderers for:

  • Issue
  • Component
  • Project Version
  • Project
  • Group
  • User

The default renderer is used just to show general data.

When To Use KCF-Pro

We see two immediate usage of KCF-Pro:

  • Dynamic choices
  • Huge Datasets, when the user must filter via autocomplete.

The plugin functionality overlaps with UGP-Pro and partially with DBCF.

  • No labels