Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-25732

Cascade select secondary value must be specified as an id

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Fix
    • Medium
    • None
    • 4.4.1
    • None

    Description

      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 .

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-25034 Multi-select custom field value handling incompatible with previous releases

          • High - High priority issues
          • Closed
          was cloned as

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-27269 SOAP getIssue - cascade select now returned as id instead of value on JIRA 5.0

          • Low - Low priority issues
          • Closed

          Activity

            People

              tcampbell Trevor Campbell (Inactive)
              bob.swift@charter.net Bob Swift OSS (Bob Swift Atlassian Apps)
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: