Redmine Computable Custom Field

🐛 Thanks for taking the time to fill out this bug report! 😊

What did you expect?¶

When changing the positions of possible values of a custom field with key/value format I would expect that calculations based on position values are still correct.

What has happened instead?¶

Custom values are untouched after changing positions of custom field enumerations. This maps old custom values with old position values with other custom field enumerations as expected.

What could be a possible solution?¶

Custom field values need to be updated with their new position number to identify the changed enumeration.

How can we reproduce the problem?¶

1. Create a computable custom field and an issue using this computation.
2. Change the position of a possible value (custom field enumeration) of that field.
3. Look at the computed value in the issue.

In what environment are you running the plugin?¶

Please copy and paste your environment information as displayed in Administration » Information or run bin/about in the root dir of your Redmine instance.

redmine_computable_custom_field version 3.0.5

What browsers are you seeing the problem on?¶

• Firefox
• Chrome
• Safari

Relevant log output¶

# Copy your log output (log/production.log) here

n/a