
| Key: |
JRA-12056
|
| Type: |
Improvement
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Steve Bachinsky
|
| Votes: |
2
|
| Watchers: |
2
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
Enterprise version... I believe other details are N/A to this issue.
|
|
Issue Links:
|
|
|
| Participants: |
Steve Bachinsky
|
| Since last comment: |
1 year, 29 weeks, 6 days ago
|
| Labels: |
|
When we attempt to perform a bulk edit on several cases to "Change the Fix Version/s", the behavior is that the field values provided in the bulk edit are additive – meaning that the values just get added to the existing values in the multi-selector for the "Fix Version/s" field and we can't get the old values removed. Is this expected behavior? If so, this is a problem when we have a number of cases that we planned to fix for one version and need to bulk change them to fix for a different version.
Ideally, there should be a "retain original values" checkbox to allow the semantics to be either additive or replacement.
Thanks, Steve
|
|
Description
|
When we attempt to perform a bulk edit on several cases to "Change the Fix Version/s", the behavior is that the field values provided in the bulk edit are additive – meaning that the values just get added to the existing values in the multi-selector for the "Fix Version/s" field and we can't get the old values removed. Is this expected behavior? If so, this is a problem when we have a number of cases that we planned to fix for one version and need to bulk change them to fix for a different version.
Ideally, there should be a "retain original values" checkbox to allow the semantics to be either additive or replacement.
Thanks, Steve |
Show » |
|