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

SOAP getIssue - cascade select now returned as id instead of value on JIRA 5.0

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Fix
    • Low
    • None
    • 5.0
    • None

    Description

      Given all the trouble with these fields for the past year, I am not sure if this change was intensional or some code was not moved correctly to the 5.0 level (I haven't looked at 4.4.5 yet). Testing against 5.0 and found the tests broke between 5.0-rc1 and 5.0. Here is the conditioning I now have to have in my tests 

      cascadeSelectByValue = (info?.version > '4.4') && (info?.version < '5.0')

      In other words, after 4.4 got values and after 5.0 it reverted back to pre 4.4 support (ids).

      Attachments

        Issue Links

          is cloned from

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-25732 Cascade select secondary value must be specified as an id

          • Medium - Medium priority issues
          • Closed
          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

          Activity

            People

              Unassigned Unassigned
              bob.swift@charter.net Bob Swift OSS (Bob Swift Atlassian Apps)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: