Project

General

Profile

Actions

Defect #35039

closed

API create issue relation method returns undefined method `split' when issue id is sent as integer

Added by Marius BĂLTEANU over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
REST API
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:

Description

Extracted from #33418#note-20:

hi everyone! I am the owner of redmine-java-api project (https://github.com/taskadapter/redmine-java-api).
I get a server error with Redmine 4.2.0 when trying to create a relation with the request body that previously worked for Redmine 3.x:

{"relation"=>{"issue_to_id"=>576, "relation_type"=>"relates"}, "issue_id"=>"575"}

> 

the error is:

NoMethodError (undefined method `split' for 576:Integer):

> 

because issue_to_id is now expected to be a string with commas, instead of a number.

is this a permanent change or just an experiment? it would be too expensive to maintain compatibility for multiple redmine versions in the java library.


Files


Related issues

Related to Redmine - Feature #33418: Bulk addition of related issuesClosedMarius BĂLTEANU

Actions
Actions #1

Updated by Marius BĂLTEANU over 3 years ago

Actions #2

Updated by Marius BĂLTEANU over 3 years ago

Here is a fix for this with test included. The patch also improve an existing test.

All tests passs: https://gitlab.com/redmine-org/redmine/-/pipelines/281875242

Actions #3

Updated by Alex Last over 3 years ago

hi Marius! would you also be interested in redmine-java-api library maintenance? feel free to submit PRs at https://github.com/taskadapter/redmine-java-api when Redmine REST API changes.

Actions #4

Updated by Guillermo ML over 3 years ago

I had the same error using python-redmine trying to relate two issues in a Bitnami VM with Redmine 4.2.0.
After applying Marius' patch and restarting the VM the error disappears and the relation is created.

Thank you!

Actions #5

Updated by Go MAEDA over 3 years ago

  • Status changed from Confirmed to Resolved
  • Assignee set to Go MAEDA
  • Resolution set to Fixed

Committed the fix. Thank you.

Actions #6

Updated by Go MAEDA over 3 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF