View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0029689 | mantisbt | ui | public | 2022-02-25 19:05 | 2022-04-02 06:03 |
Reporter | sandyj | Assigned To | atrol | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | duplicate | ||
Product Version | 2.25.2 | ||||
Summary | 0029689: Summary field is lost when pressing back button after hitting an error when reporting an issue | ||||
Description | When reporting an issue, and if I have missed a mandatory field such as category or custom field and submit the issue, I get the Application error 11 and am instructed to press back to correct the issue. When I hit the back button all data is retained but the Summary field is empty. The same happens when I hit the security token timeout error. | ||||
Steps To Reproduce |
Description and other data entered is retained but the summary field is empty. | ||||
Tags | No tags attached. | ||||
I guess this is the same like 0028618 , so this should be fixed in 2.26.0 There could be more browsers that don't support the "required" HTML attribute and there could be more reasons to throw an application error. |
|
Yes, as mentioned above, the same thing happens when hitting application error #2800 which would not be addressed in 2.26.0. Not sure if this matches the scenario "any field Content that is in sequence BEFORE this reported mandatory field gets saved, but any field Content that is in sequence AFTER the empty field gets lost." as Summary is lost but Description is retained. Is description sequenced before Category and Summary after? But if the fix is to ensure every field Content is saved in the local cache then this should fix this issue. |
|