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

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

            [JRASERVER-27269] SOAP getIssue - cascade select now returned as id instead of value on JIRA 5.0

            Bugfix Automation Bot made changes -
            Minimum Version New: 5
            Owen made changes -
            Component/s Original: Ecosystem - SOAP & XML-RPC API [Obsolete] [ 10480 ]
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2842695 ] New: JAC Bug Workflow v3 [ 2919485 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2577168 ] New: JAC Bug Workflow v2 [ 2842695 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1541009 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2577168 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: bughunt_java New: affects-server bughunt_java
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 672700 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1541009 ]
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v5 [ 655763 ] New: JIRA Bug Workflow w Kanban v6 [ 672700 ]
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v5 [ 372641 ] New: JIRA Bug Workflow w Kanban v6 [ 655763 ]

            Bob Swift added a comment -

            I understand and agree with the direction, however, there needs to be a difference between not making improvements and fixing obvious regression problems and introducing incompatibilities. This can cause major headaches for upgrades. For an interface that was suppose to be stabilized, there has been a lot of breakage in the 4.x/5.0 time period. Please ensure SOAP APIs retain upward compatibility and regressions get fixed.

            Bob Swift added a comment - I understand and agree with the direction, however, there needs to be a difference between not making improvements and fixing obvious regression problems and introducing incompatibilities. This can cause major headaches for upgrades. For an interface that was suppose to be stabilized, there has been a lot of breakage in the 4.x/5.0 time period. Please ensure SOAP APIs retain upward compatibility and regressions get fixed.

              Unassigned Unassigned
              bob.swift@charter.net Bob Swift
              Affected customers:
              0 This affects my team
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: