Web Staff Client: Reports description field required
Bug #1709698 reported by
Terran McCanna
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Low
|
Unassigned |
Bug Description
Tested as of 2.12.2
When creating a new report template, I cannot save it without entering something into the description field. I don't see why that would be a required field.
Changed in evergreen: | |
status: | New → Confirmed |
Changed in evergreen: | |
assignee: | nobody → Rogan Hamby (rogan-hamby) |
Changed in evergreen: | |
assignee: | Rogan Hamby (rogan-hamby) → nobody |
Changed in evergreen: | |
milestone: | 3.next → 3.4-beta1 |
Changed in evergreen: | |
milestone: | 3.4-beta1 → 3.3.0 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The description field on reporter.template has actually always been marked NOT NULL. IIRC, the intention was to strongly encourage staff to enter a meaningful description of the report, and (also IIRC) the decision on that didn't come from the developers.
There are several ways we could address this: make the field NULLABLE in the database; default it to and empty string instead of undefined in the UI; mark it as required and have the form complain and refuse to submit (which would address any post-save failure caused by this requirement, if that's possible today -- I don't recall).
Are there broader thoughts from the community?