View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0036970 | mantisbt | ui | public | 2026-03-13 12:01 | 2026-03-14 09:03 |
| Reporter | raspopov | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Product Version | 2.28.0 | ||||
| Summary | 0036970: The forgotten "Due Date" field | ||||
| Description | While debugging the DateTimePicker, I discovered some existing pages intended for entering the “Due Date” field value, but for some reason they weren't being used. For example:
However:
It feels, as if the code was simply left unfinished. | ||||
| Tags | No tags attached. | ||||
|
Feature was introduced in 1.3.0, see 0019929. |
|
|
The action is available from the group update selection list, provided you have due_date_update_threshold. It works correctly, as far as I can tell... |
|
|
Thanks for the info—I missed that this works via a group operation, and I thought I was updating “dead code” while working on the DateTimePicker PR. So, should we add an “Update Due Date” button directly to the “view.php” page? Or maybe add to it a selection list element purely for ease of use, considering that there might be a user without general permissions but with the right to move dates? |
|
I don't think that's necessary, when a single Issue's due date needs to be updated, you can just edit the Issue and change it
You mean in the case of a user that has due_date_update_threshold but not update_bug_threshold ? Technically possible but kind of weird scenario.
Not sure what you mean |
|