Cascade select secondary value must be specified as an id

XMLWordPrintable

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Medium
    • None
    • Affects Version/s: 4.4.1
    • Component/s: None
    • 4.04

      With the fix for JRA-25034 to make specifying custom field values consistently allow the user seen value (in addition to the value id), the secondary value for a cascade select is not handled. It must still be specified as an id. The returned value when retrieving the data is now returned in the user seen value .

            Assignee:
            Trevor Campbell (Inactive)
            Reporter:
            Bob Swift
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: