Cloud MLTF

Multi Level & Tree Fields lets you model unlimited‑depth hierarchies and reuse them across custom fields.

You define one or more Options Trees, then create MLTF field types that reference those trees. Users select values while creating or editing work items.

Options Trees

An Options Tree is the reusable data source for your MLTF fields. You can have multiple trees for different use cases.

Create a tree

Go to Apps → MLTF → Options Trees and click Create Options Tree.
Give it a clear name (e.g., Product Catalog, Location Hierarchy).

Manage options & levels

Click Options on a tree to add items.
Level‑1 options: Create Option.
Child options: click the + next to a parent to add sub‑options.

Options Trees Operations

Delete & Sort

Delete Options

Sort Options

Rename & Enable/Disable

Edit Options

Important: Editing options does not change existing work items. New or edited options apply going forward. Historical work items retain the previously selected values.

Enable / Disable Options

When an option is disabled, its child options will be disabled as well.

Expand/Collapse & Return to Options Trees

Expand & Collapse

Return to Options Trees

Export & Import

Export as XML, CSV or JSON

Export as XML, CSV or JSON
Find the import templates below

MLTF supports XML, CSV, and JSON for bulk operations. Export before large edits; keep backups.

Re‑install safety: If you ever uninstall MLTF, export all trees first. After reinstalling, import using Merge with existing to retain original IDs and avoid breaking references.

Import Templates

You can download the import templates below.

Column Details

Columns (all mandatory): ID | Value | Enable | Parent

Rules:

ID: unique integer per option.
Value: the label shown to users.
Enable: TRUE or FALSE.
Parent: use -1 for top‑level items; otherwise set to the ID of the parent option.

ID (Each option should have an ID)	Value (Your options’ name)	Enable (Indicate the option is enabled or disabled - TRUE / FALSE)	Parent (For the first levels of all options use the “-1“, for others use the ID column)

ID (Each option should have an ID)	Value (Your options’ name)	Enable (Indicate the option is enabled or disabled - TRUE / FALSE)	Parent (For the first levels of all options use the “-1“, for others use the ID column)
1	Option 1	TRUE	-1
2	Option 1-1	TRUE	2
3	Option 2	TRUE	-1
4	Option 2-2	TRUE	3

Multi Level Custom Field Types

Use the plugin’s five MLTF field types to tap into your Options Trees—create the custom fields you need, then add them to the appropriate screens and workflows.

Multi Level (Advanced Cascading)

Multi Level (Cascading)

Option Path (Multi Select)

Option Path (Single Select)

Tree (Multi Select)

Tree (Single Select)

Multi Level (Advanced Cascading)

With Multi Level (Cascading), teams can navigate deeply nested option hierarchies in a single field, making issue categorization faster and more consistent. field covers your entire hierarchy.

Create one and you’re set.

Select Multi Level (Advanced Cascading) → Configure → Choose Options Tree.

For each level in the hierarchy, you can assign a distinct field type — Radio Button, Single Select, Multi Select, or Checkbox — tailored to your data entry needs.

Advanced Cascading on Work Item

Multi Level (Cascading)

A single Multi Level (Cascading) field covers your entire hierarchy. Create one and you’re set.

Select Multi Level (Cascading) → Configure → Choose Options Tree.

Auto-select next level (optional): Auto-pick the only child and continue

Cascading on Work Item

Option Path (Multi Select or Single Select)

Create an Option Path field (choose Single-select or Multi-select).

Open the field’s configuration → Options Tree mapping → select your Options Tree and Save.

Displays the full path (e.g., Region > Country > City) as the selectable value.

Toggle “Only leaf options are selectable” to enforce choosing the lowest level. Disable it to allow picking any level along the path.

Toggle “Load options dynamically”: If disabled, all options you’ve defined are listed. If enabled, only the first 100 levels are shown initially.

Choose single or multi‑select based on your use case.

Option Path on Work Item

Tree (Multi Select or Single Select)

Visual, expandable tree component for choosing items.

Create Tree type of field as multi select or single select.

Then edit option tree mapping, select Options Tree.

Only leaf options selectable: same behavior as above.

Collapse options: start with options collapsed for faster scanning.

Tree on Work Item

Jira Service Management

MLTF fields are fully supported on customer portal forms. Include them where needed—and set them as required.

Dashboard & Gadgets

MLTF provides dedicated gadgets that allow you to visualize and analyze your hierarchical field data directly on Jira dashboards — no exports, no manual work.

Add the MLTF Level-Based Report gadget to your Jira dashboard.

Data source — Select a saved filter (JQL) that returns the issues you want to analyze.

Field — Select the MLTF field to report on. The gadget will automatically detect the hierarchy depth.

Levels — Choose how many levels to display in the report, from 1 up to a maximum of 5 levels.

Visualization — Select your preferred chart type for the breakdown.

💡 Tip: Use a focused JQL filter (e.g. by project, sprint, or date range) to keep your dashboard gadgets meaningful and fast-loading. Broad filters across large datasets may affect gadget performance.

Search Work Items

Use Multi Level fields directly in JQL searches for precise filtering.
Add them as columns in issue navigator and easily export results with full hierarchy context.

Available JQL Functions

For each MLTF field, the following JQL properties are available:

Function	Description

Function	Description
`FieldName.Value`	The full selected value as displayed on the issue
`FieldName.Path`	The complete path from root to the selected option (e.g. `Product & Engineering/Product Management/Roadmap Planning`)
`FieldName.FirstLevelOption`	The value selected at Level 1
`FieldName.SecondLevelOption`	The value selected at Level 2
`FieldName.ThirdLevelOption`	The value selected at Level 3
`FieldName.FourthLevelOption`	The value selected at Level 4
`FieldName.FifthLevelOption`	The value selected at Level 5
`FieldName.SixthLevelOption`	The value selected at Level 6
`FieldName.SeventhLevelOption`	The value selected at Level 7

"Affected Business.Path" = "Network/Peering Partner/Zayo"

Search work items by defining the full path

"Affected Business.Value" = "Core Router"

Search work items that have specific values, including sub-options

Filter all issues where the top-level business unit is Product & Engineering:

"Affected Business.FirstLevelOption" = "Product & Engineering"

Filter issues under a specific department:

"Affected Business.SecondLevelOption" = "Product Management"

Combine multiple levels for precise filtering:

"Affected Business.FirstLevelOption" = "IT & Security"
AND "Affected Business.ThirdLevelOption" = "Threat Detection"

💡 Tip: Use FieldName.Path when you need an exact match across the full hierarchy. Use level-specific properties (FirstLevelOption, SecondLevelOption, etc.) when you want to aggregate or filter broadly at a particular depth — for example, finding all issues affecting a business unit regardless of the sub-department selected.

Keeping Your Data in Sync — When and How to Re-index

To ensure accurate results in JQL searches and dashboard gadgets, MLTF fields need to be indexed. If you notice missing or outdated data in your reports or search results, running a re-index will resolve it.

When Should You Re-index?

You should run a re-index in the following situations:

For Reporting & JQL Accuracy If your JQL queries return unexpected results or your dashboard gadgets are not reflecting the data you expect, a re-index will ensure your MLTF field data is fully up to date and accurately represented.

After Changing an Option Value in Your Tree If you rename or update an option in your Options Tree, that change does not automatically reflect on existing issues. A re-index is required to propagate the updated value across all affected issues.

⚠️ Without re-indexing after an option rename, your issues will continue to display the old value and JQL queries using the new value will return no results.

How to Re-index

Navigate to Apps → MLTF → Reindex.
Select the field you want to re-index.
Optionally, enter a JQL query to narrow the scope and re-index only the relevant issues — for example, a specific project, issue type, or date range.
Click Start Reindex.

💡 Tip: Use a JQL scope whenever possible. Re-indexing a targeted subset of issues is significantly faster than re-indexing your entire instance, especially in large Jira environments.