Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

return 0 for empty custom field values #122

Closed
andrew-klepcha opened this issue Mar 1, 2016 · 2 comments
Closed

return 0 for empty custom field values #122

andrew-klepcha opened this issue Mar 1, 2016 · 2 comments
Assignees
Labels
bug

Comments

@andrew-klepcha
Copy link

@andrew-klepcha andrew-klepcha commented Mar 1, 2016

I use version 1.5.0 of python-redmine. A problem appeared after I added some custom fields to existing tasks in Redmine. These are list-type fields. When I am trying to update an issue (for other fields, not for the newly created ones), a Validation Error for issue.save() appears .
As a workaround, I changed all custom fields that == 0 to an empty string.
I think that changing "return 0" to "return ''" (empty string) in redmine/resources.py:850 may help.

@maxtepkeev maxtepkeev added the bug label Mar 26, 2016
@maxtepkeev maxtepkeev self-assigned this Mar 26, 2016
@maxtepkeev
Copy link
Owner

@maxtepkeev maxtepkeev commented Mar 26, 2016

Hi,

Sorry for making you wait for so long for the response.

I believe that if there is such a bug it depends on the Redmine version being used, I wan't able to reproduce it with Redmine 3.2.0.

Can you please tell me what Redmine version do you use ?

maxtepkeev added a commit that referenced this issue Mar 27, 2016
@maxtepkeev
Copy link
Owner

@maxtepkeev maxtepkeev commented Mar 27, 2016

It seems that this was only possible for Redmine < 2.5.0.

Your proposed solution is now used in v1.5.1. Thanks.

@maxtepkeev maxtepkeev closed this Mar 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.