Reports: transform selection is sticky
Bug #1778521 reported by
Anna Goben
This bug affects 26 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
3.3 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Template field transform settings, once chosen in the selector, are sticky, even when it invalidates the datatype of other entries in the template editor. It travels as a sticky setting, despite not showing in the Transform box, into other sources being used to build the template until the person writing the report goes to an entry of the same type as the original was selected when the transform was chosen and deselects the transform. It should not be possible to apply a date transform to text or IDs or an average transform to text or IDs when writing/editing a template.
I've observed this behavior since 3.0. Currently using 3.1 on Chrome.
Changed in evergreen: | |
status: | New → Confirmed |
summary: |
- Web Client: Report transform settings are sticky + Reports: transform selection is sticky |
tags: | added: reports |
Changed in evergreen: | |
importance: | Undecided → Medium |
no longer affects: | evergreen/3.2 |
Changed in evergreen: | |
milestone: | 3.5-alpha → 3.4.3 |
no longer affects: | evergreen/3.4 |
tags: | added: signedoff |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This is so aggravating, so I'm adding heat. I constantly forget that I need to double-check my transforms and then my report fails.