Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-10333

Updating epic link field through REST causes 500 Internal Error

XMLWordPrintable

      Was raised as part of a support ticket.
      This seems to be caused because the EpicLinkCFType returns an IssueImpl object, which at the side of JIRA gets casted to a String (which throws an exception) (see TextCustomFieldOperationsHandler.getInitialValue()).
      It's considered to be a TextCustomFieldOperationsHandler because of this check in CustomFieldImpl:

      public RestFieldOperationsHandler getRestFieldOperation()
    {
        CustomFieldType customFieldType = getCustomFieldType();
        if (customFieldType instanceof RestCustomFieldTypeOperations)
        {
            return ((RestCustomFieldTypeOperations) customFieldType).getRestFieldOperation(this);
        }
        return new TextCustomFieldOperationsHandler(this, getI18nHelper());
    }

            [JSWSERVER-10333] Updating epic link field through REST causes 500 Internal Error

            Boo added a comment -

            We have the same Jira Cloud/Aha! scenario as Mr Zaluckis above - please confirm resolution status

            Boo added a comment - We have the same Jira Cloud/Aha! scenario as Mr Zaluckis above - please confirm resolution status

            Vladislavs Zaluckis added a comment -

            Hi!

            This issue seems to be fixed, but has it been actually rolled out to JIRA Cloud? I am using Aha! integrated with JIRA Cloud, and there is this issue with synchronizing Epics: https://support.aha.io/hc/en-us/articles/205401525-Your-epic-name-or-description-isn-t-updated-from-JIRA-to-Aha- which links to this issue. The synchronization still does not work, so I wonder whom should I poke?

            Vladislavs Zaluckis added a comment - Hi! This issue seems to be fixed, but has it been actually rolled out to JIRA Cloud? I am using Aha! integrated with JIRA Cloud, and there is this issue with synchronizing Epics: https://support.aha.io/hc/en-us/articles/205401525-Your-epic-name-or-description-isn-t-updated-from-JIRA-to-Aha-  which links to this issue. The synchronization still does not work, so I wonder whom should I poke?

            Jas Panesar added a comment - - edited

            Appears fixed as per status of this ticket, trying out!

            Jas Panesar added a comment - - edited Appears fixed as per status of this ticket, trying out!

            Bob Swift added a comment - - edited

            I believe this fixed caused JSW-13830 since this was about the only thing in 6.7.14.

            Bob Swift added a comment - - edited I believe this fixed caused JSW-13830 since this was about the only thing in 6.7.14.

            Martin Tints added a comment -

            The workarounds do not work (Jira 7.0.10). Please help, very annoyed with this.

            Martin Tints added a comment - The workarounds do not work (Jira 7.0.10). Please help, very annoyed with this.

            Marek Pazik (Inactive) added a comment - - edited

            There is workaround for this issue.
            The public REST Api provides resources that do equivalent work:
            https://docs.atlassian.com/greenhopper/REST/cloud/#agile/1.0/epic-moveIssuesToEpic
            https://docs.atlassian.com/greenhopper/REST/cloud/#agile/1.0/epic-removeIssuesFromEpic

            Marek Pazik (Inactive) added a comment - - edited There is workaround for this issue. The public REST Api provides resources that do equivalent work: https://docs.atlassian.com/greenhopper/REST/cloud/#agile/1.0/epic-moveIssuesToEpic https://docs.atlassian.com/greenhopper/REST/cloud/#agile/1.0/epic-removeIssuesFromEpic

            Harinder Singh added a comment -

            Hi pals,
            any update on this issue ?

            Harinder Singh added a comment - Hi pals, any update on this issue ?

            Tim Thompson added a comment - - edited

            Well ain't this a bummer. It seems that it has been working all along; however, the MSXML2.XMLHTTP returns a status of 1223 (Unknown) instead of a valid 204 "no content" and so Excel VBA craps out. Took a lot of digging, but stumbled across a note stating

            "XMLHTTPRequest implementation in MSXML HTTP (...) does not handle HTTP responses with status code 204 (No Content) properly; the `status' property has the value 1223.".

            I just ignore the error and the world is fine. No content is exactly what is expected back and ONLY a successful SEND would cause the error because no content is returned.

            Thanks Douglas - your workaround is now working for me. Still would like to see a proper fix for the JIRA REST API handling of the EPIC LINK field.

            Tim Thompson added a comment - - edited Well ain't this a bummer. It seems that it has been working all along; however, the MSXML2.XMLHTTP returns a status of 1223 (Unknown) instead of a valid 204 "no content" and so Excel VBA craps out. Took a lot of digging, but stumbled across a note stating "XMLHTTPRequest implementation in MSXML HTTP (...) does not handle HTTP responses with status code 204 (No Content) properly; the `status' property has the value 1223.". I just ignore the error and the world is fine. No content is exactly what is expected back and ONLY a successful SEND would cause the error because no content is returned. Thanks Douglas - your workaround is now working for me. Still would like to see a proper fix for the JIRA REST API handling of the EPIC LINK field.

            Tim Thompson added a comment -

            As far as I can tell everything is setup correctly. I have several other transactions working (GETs, POSTs) - this seems to be
            1. Known Atlassian EPIC LINK issue through the published API.
            2. ALTERNATE APPROACH - /greenhopper: Some weird thing going on in VBA with the MSXML2.XMLHTTP object in it's parsing of a JSON object with array structure "[ ...]". If I remove the array "[....]" it goes through and I get the expected JIRA-side error response.

            I think I'm cursed.

            Tim Thompson added a comment - As far as I can tell everything is setup correctly. I have several other transactions working (GETs, POSTs) - this seems to be 1. Known Atlassian EPIC LINK issue through the published API. 2. ALTERNATE APPROACH - /greenhopper: Some weird thing going on in VBA with the MSXML2.XMLHTTP object in it's parsing of a JSON object with array structure "[ ...]". If I remove the array " [....] " it goes through and I get the expected JIRA-side error response. I think I'm cursed.

            Douglas Orttenburger added a comment -

            are your authentication headers setup correctly?

            I don't know VBA at all, so I wouldn't be much help here

            Douglas Orttenburger added a comment - are your authentication headers setup correctly? I don't know VBA at all, so I wouldn't be much help here

              Unassigned Unassigned
              jderaedt Jeroen De Raedt
              Affected customers:
              70 This affects my team
              Watchers:
              51 Start watching this issue

                Created:
                Updated:
                Resolved: