Web Staff Client - Problems cloning existing reports
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned | ||
3.0 |
Fix Released
|
Medium
|
Unassigned | ||
3.2 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
There are several cloning issues in the 2.11 web client that occur when cloning a template that was originally created in the xul interface:
1) It doesn't open in the standard template editing interface, which is confusing (see screenshot comparing the two)
2) The "Enable nullability selection" checkbox is missing
3) If you had a Boolean value set as a filter in the original template (such as Deleted Equals False), the value doesn't carry over or allow you to set it
4) It doesn't allow you to add additional fields, or even display the other fields that are available
If any of this was intentional due to major changes on the back end, then it would be helpful to users if there were an on-screen message to inform them that they will have to re-create those templates from scratch in the new interface.
Changed in evergreen: | |
milestone: | none → 3.0-alpha |
Changed in evergreen: | |
milestone: | 3.0-beta → 3.0-beta2 |
Changed in evergreen: | |
milestone: | 3.0-beta2 → 3.0-rc |
Changed in evergreen: | |
milestone: | 3.0-rc → 3.0.1 |
Changed in evergreen: | |
milestone: | 3.0.1 → 3.0.2 |
Changed in evergreen: | |
milestone: | 3.0.2 → 3.0.3 |
Changed in evergreen: | |
milestone: | 3.0.3 → 3.0.4 |
Changed in evergreen: | |
milestone: | 3.0.4 → 3.0.5 |
Changed in evergreen: | |
milestone: | 3.0.5 → 3.0.6 |
Changed in evergreen: | |
milestone: | 3.0.6 → 3.0.7 |
Changed in evergreen: | |
milestone: | 3.0.7 → 3.0.8 |
Changed in evergreen: | |
milestone: | 3.0.8 → 3.1.3 |
Changed in evergreen: | |
milestone: | 3.1.3 → 3.1.4 |
Changed in evergreen: | |
milestone: | 3.1.4 → 3.1.5 |
Changed in evergreen: | |
assignee: | nobody → Kathy Lussier (klussier) |
Changed in evergreen: | |
assignee: | Kathy Lussier (klussier) → nobody |
Changed in evergreen: | |
milestone: | 3.1.5 → 3.1.6 |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
I agree with Terran on the above issues. Initially, I was thinking we should break these issues out into separate bugs, but everything boils down to issue #1. If we were using the standard template creation interface to clone templates, we would have all of the items reported in 2, 3 and 4.
We are losing a bit of functionality by cloning reports this way.