Table of Contents | ||
---|---|---|
|
Info |
---|
Multi Level & Tree Field app provides select type custom fields that can be connected to a defined options tree and added to appropriate issue or workflow screens. Please refer to Configuration for more information. |
Creating an Issue
Multi Level
In the example below the user first selects the "Hardware" option from the "Problem in" custom field.
1
The next connected sub-field options are then populated automatically as "Notebook", "Phone" and "Printer"
2
Next, an option from the second connected field is selected. Once this is done, options in the third field are populated automatically.
3
Finally, an option from the last connected field is selected.
Cascading
Affected Business: Subfields will appear as you select the options based on the number of levels you have.
Option Path (Multi-select)
Tree (Multi-select)
Viewing Multiple Levels Within Issues
Issues that have
multi-level custom fields on their configured issue view screens will display selected option values next to the field label, as is with all custom fields.
Editing Multiple Levels
Multi Level fields can be added to Edit Issue screens
When using inline edit -> if a multiple level field is being edited in inline edit mode, a
. A pop-up dialogue will show up
- If the selected field option is changed the value in the connected field will be purged and the options will be automatically populated for a new selection
- When the sub-field is edited inline, the pop-up will not show the parent field.
Multimedia | ||||||||
---|---|---|---|---|---|---|---|---|
|
for editing levels.
Issue Search Column View
Multiple Level fields can be used within the JQL search.
Fields also can be added to columns and can be exported.
You can search issues by defining the full path:
"CustomField Name" in optionWithFullPath("Hardware/Notebook/Lenovo")
OR
"CustomField Name" in optionWithFullPath("Hardware//Notebook//Lenovo")
You can search
"CustomField Name" in withSubOptions("Lenovo")
withSubOptions() function can take more than one arguments: withSubOptions("", "", ...)
for issues that have specific values, including sub-options.