Tuleap Community Edition development and releases are no longer public. You have until September 30th to download packages and sources in Tuleap project. You can contact the team if you need further assistance.

    •  
      request #20146 Jira worklog import is not compatible with Jira REST API v2
    Infos
    #20146
    Yannis ROSSETTO (rossettoy)
    2021-03-29 15:26
    2021-03-29 11:10
    21743
    Details
    Jira worklog import is not compatible with Jira REST API v2

    After switching the Jira REST API version from v3 to v2, we got the following fatal error:

    PHP Fatal error: Uncaught TypeError: Argument 1 passed to Tuleap\Timetracking\JiraImporter\Worklog\WorklogComment::buildFromAPIResponse() must be of the type array, string given, called in /usr/share/tuleap/plugins/timetracking/include/Timetracking/JiraImporter/Worklog/Worklog.php on line 96 and defined in /usr/share/tuleap/plugins/timetracking/include/Timetracking/JiraImporter/Worklog/WorklogComment.php:41 Stack trace: #0 /usr/share/tuleap/plugins/timetracking/include/Timetracking/JiraImporter/Worklog/Worklog.php(96): Tuleap\Timetracking\JiraImporter\Worklog\WorklogComment::buildFromAPIResponse() #1 /usr/share/tuleap/plugins/timetracking/include/Timetracking/JiraImporter/Worklog/WorklogRetriever.php(65): Tuleap\Timetracking\JiraImporter\Worklog\Worklog::buildFromAPIResponse() #2 /usr/share/tuleap/plugins/timetracking/include/Timetracking/JiraImporter/JiraXMLExport.php(122): Tuleap\Timetracking\JiraImporter\Worklog\WorklogRetriever->getIssueWorklogsFromAPI() #3 /usr/share/tuleap/plugins/timetracking/include/Timetracking/JiraI in /usr/share/tuleap/plugins/timetracking/include/Timetracking/JiraImporter/Worklog/WorklogComment.php on line 41

    Other
    Empty
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Yannis ROSSETTO (rossettoy)
    Closed
    2021-03-29
    Attachments
    Empty
    References
    Referenced by request #20146

    Follow-ups

    User avatar
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes