Skip to end of banner
Go to start of banner

Cloud MLTF Fields On Issue

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 3 Next »

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 Cascading


Affected Business: Subfields will appear as you select the options based on the number of levels you have.


Affected Business: Subfields will appear as you select the options 
based on the number of levels you have.


Option Path (Multi-select)

Feilds of Interest: 


Tree (Multi-select)

Location: 





Viewing Multiple Levels Within Issues

Issues that have multiple 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

Multiple Level fields can be added to Edit Issue screens, the behavior there is similar to that in the Create Issue screens. 



When using inline edit -> if a multiple level field is being edited in inline edit mode, a pop-up dialogue will show up. The pop-up will display the edited field and its connected fields (but not fields in the upper category levels).

  • 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.




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.


JQL Functions


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 issues with sub-options:

"CustomField Name" in withSubOptions("Lenovo")

withSubOptions() function can take more than one arguments: withSubOptions("", "", ...)

  • No labels