Introduction

The Adaptive Custom Fields app enables Jira administrators to create multi contexts (subcontexts) for one project and allows the delegation of options management. An AI sorting algorithm, rich user interface with emoticons and colors, along with an options description will help your Jira users to select the right options faster.

Using Adaptive Custom Fields instead of native fields can give you the following advantages

When in particular you should use Adaptive Custom Fields

Main features

For Jira administrators

Subcontexts let you define multi contexts for the same project

Context management

Jira allows only one Context per project. Without Adaptive Custom Fields you can’t have multiple different contexts/configurations for one project. To change this, we have created subcontexts. Thanks to these, it is now possible to have more than one field subcontext/configuration for the same project. For example a different set of options for different issue types in the same project. In the example above, Bugs in the NOD project have a different set of options from Stories in the same NOD project.

Use the Create Subcontext dialog to quickly define a Subcontext with options and description. Contexts are defined for issue type(s) and project(s). A Subcontext can be defined for a subset of the context’s projects and issue types. This way, you gain an additional level of configuration without losing control while still leveraging Jira’s native features.

Automatic options sorting

You don’t need to manually define the order of options. ACF ships with an algorithm that will do it for you. Based on the frequency and a few other parameters, it will automatically find the best options order for every subcontext. Depending on the field usage, the algorithm may need a few days to warm up and gather enough data to work precisely. To use it change sorting to AI on the Subcontexts page.

More about subcontext

ACF creates a default subcontext automatically when the field is created. Initially, its scope matches the Jira Context scope. A default subcontext defines how the field behaves for projects and issue types not used in other subcontexts. ACF fields are visible in the whole Jira context, subcontexts define how the ACF fields work.

Jira has two types of context: a global, defined context for all projects and a normal context for one or more projects. A normal context overwrites the global context, and the same rule applies to the ACF app. A normal context subcontext overwrites the global context subcontext. For example, in the following scenario:

In project A, issue type A field A will have options C and D. Subcontext B will overwrite subcontext A.

A centralized list of options shared in many contexts

Context management

In Jira, every field’s context has its list of options. In Adaptive Custom Fields, the option definitions (name, color, icon) are global. You can decide in which context the given option is visible. This makes options management easier and helps to keep options in order. You can do bulk operations such as adding, removing, or updating options from many subcontexts on one page in just a few clicks.

When adding an option you can define its value, subcontexts in which the option will be visible, background or border, color, and icon. When an option is created, you can additionally add a description and disable an option.

Options CSV import export

Thanks to CSV import and export you can easily move your options from and to the Adaptive Custom Fields app. This is an example of an exported CSV. You can use it in custom fields migration.

Options management delegation

Context management

You can delegate Adaptive Fields Management to project administrators. Project administrators can add/edit/delete their own projects’ subcontext(s). Project administrators can create new options, assign options to their own projects’ subcontexts. Project administrators can edit options if they are used only in their projects. Jira Administrators control the Jira contexts, you keep full control and can decide who can edit what. Please note that Free Jira edition does not support project permissions, you can’t delegate options management in Jira free edition.

For users

A new easier to use user interface designed for 100+ options

The new UX allows users to select the right options faster. Smart sorting keeps the most needed options at the top of the list. The option's description is available on mouse hover.

Simplified view with options description

When the user filters options, the view adjusts to the number of available options, and the simplified view shows every option's description inline.

How it works

🔒 The app uses Forge platform, all data is stored in the Atlassian infrastructure, the app doesn’t exchange any data with the external world. We provide enterprise-level support and a transparent privacy policy.

The app uses Forge custom field type and string data type, each Adaptive field works like a regular Jira custom field with an array of strings. Jira features supported for String custom fields are supported for the Adaptive Custom Fields. Currently, we support multi- and single-select adaptive fields in company-managed projects on Jira Cloud.

Limitations and known issues

Known issues

Forge platform limitations

Tutorials

Support

Bugs, questions and feature proposals can be submitted on our support portal or by sending an email to support@nodical.co.

FAQ

The Adaptive Custom Field is not visible, why?

Like any other Jira Custom Fields, the Adaptive Custom Fields visibility is controlled by context, screens, and layouts. The good news is that for Admins, Jira provides the Where is my field feature. This will display information about where you can find the field or why the field isn’t displayed on the issue. ACF controls field configuration in the given context and subcontexts, for example showing options assigned to a given subcontext.

Why is the option not visible?

The ACF subcontext defines how a field works on the specific issue type in a given project. To show an option in a given subcontext, navigate to matching context, find the appropriate subcontext, and add an option to the options list in the options column. Please note that subcontexts from the Default/Global context can be overwritten by other contexts which may impact which options are visible to the user.

How can I share feedback or ask a question?

You can suggest a new feature, improvement and ask any question via our support portal. If you want to help us more and win an amazon voucher, please fill in the feedback form ; every third person will receive a 50$ voucher.