View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0005628 | mantisbt | feature | public | 2005-05-20 06:56 | 2023-07-03 20:13 |
Reporter | hgaland | Assigned To | |||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | new | Resolution | open | ||
Product Version | 1.0.0a2 | ||||
Summary | 0005628: Save bugs as Draft | ||||
Description | In our company, we are about to implement Mantis as a case tracker (we are the first newspaper editor in switzerland). In our context, reporters may not have necessary quiet time to report their bugs with all the details we require for resolution. I'm not a specialist in PHP, and I dont what to change the Mantis standard, so I address you this feature request. My idea was to implement a status "DRAFT" before the "NEW" status, and to give access rights to reporteurs to act on status modifications, just to post them as "NEW" when completed. I think it will be interesting to define a threshold that allow the reporteur to update the initial bug information (the info on the submission report and only that one) as long as it is not in the status corresponding to "NEW". What do you thing about that ? | ||||
Additional Information |
| ||||
Tags | patch | ||||
Attached Files | |||||
I did the implementation in our test system based on version 1.0.0a3. You will find attached the files modified to implement the feature. If the solution is acceptable for you, you can implement it in the feature release. It will be my contribution. Enjoy it anyway !!! Note: read the readme because some setting that where done in my custom files should require to be placed in MANTIS standard cinfiguration files. FEATURE OVERVIEWAll MANTIS usual access level threshold or feature defined with config_defaults_inc.php and config_inc.php are respected, including workflow features and action groups (view_all_bug_page). The only deference is that once an issue is DRAFT, it is considered as now modifiable for everybody except the reporter or at least a manager access level (global or project). In addition, as long as the issue is not NEW, the reporter or manager can update SOME FIELDS and save again. But they cannot add NOTES (nor update or delete existing notes), send reminders or create childs. IMPLEMENTATION GUIDEOnce the last modifications are done (either in standard MANTIS files or in your custom files), to activate the feature, you have to define the following in your custom_inc.php: In : config_inc.php Activate draft feature by setting the value to DRAFT |
|
Is this feature completely implemented? Can I copy the patch to incorporate the DRAFT feature? |
|
Considering that the uploaded code dates back to 2005 and was apparently developped for an alpha version of Mantis 1.0, it is highly unlikely that you will be able to apply it as-is. |
|