Defect #24994
closedCustom field's value can't be saved when updating an issue
0%
Description
Hi there,
I updated redmine from 2.3.0 to 3.3.0. Now I met a problem, below are repro steps.
1. Create a new issue
2. Update the issue to another status, which has required field in my workflow configuration. The required field is List format configured in Custom fields.
3. Choose a value in the list, save the issue successfully.
4. The filed value leaves empty after a success save.
Plus, I have some new findings. Let's call the custom field as Field-A, Field-A has three values a,b,c.
1. Set Field-A to a, save the issue.
2. The Field-A leaves empty.
3. Update the issue, set Field-A to b, save the issue.
4. The Field-A's value is successfully set to b
5. Update the issue, set Field-A to a (which is initially value in step 1), save the issue.
5. The Field-A's value is still b, but a is expected here.
If the initial value is b, the repeat steps 2-5, you will find the initial value can't be saved. But if you change the value of this field the save the issue, it works well.
Files
Updated by Toshi MARUYAMA about 8 years ago
Yao Li wrote:
Hi there,
I updated redmine from 2.3.0 to 3.3.0. Now I met a problem, below are repro steps.
1. Create a new issue
2. Update the issue to another status, which has required field in my workflow configuration. The required field is List format configured in Custom fields.
3. Choose a value in the list, save the issue successfully.
4. The filed value leaves empty after a success save.
I cannot reproduce on vanilla Redmine 3.3.2.
Updated by Toshi MARUYAMA about 8 years ago
- Status changed from New to Needs feedback
Updated by Toshi MARUYAMA about 8 years ago
Yao Li wrote:
Plus, I have some new findings. Let's call the custom field as Field-A, Field-A has three values a,b,c.
1. Set Field-A to a, save the issue.
2. The Field-A leaves empty.
3. Update the issue, set Field-A to b, save the issue.
4. The Field-A's value is successfully set to b
5. Update the issue, set Field-A to a (which is initially value in step 1), save the issue.
5. The Field-A's value is still b, but a is expected here.
I cannot understand why a is expected.
Updated by Yao Li about 8 years ago
- File hzyhlzyy-33938.pdf hzyhlzyy-33938.pdf added
Refer to step #5, I updated the field to a, so in the last step a is expected.
See attached pdf, search the field name "J离场时间" - you can see the field is saved many times but "J离场时间" field still remains empty.
Updated by Toshi MARUYAMA about 8 years ago
- Status changed from Needs feedback to Closed
- Resolution set to Invalid
You use plugins due to your #24995. Please contact plugin author.