View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0015766 | mantisbt | feature | public | 2013-04-18 10:33 | 2013-11-14 05:55 |
Reporter | david_stephensen | Assigned To | |||
Priority | normal | Severity | feature | Reproducibility | have not tried |
Status | new | Resolution | open | ||
Summary | 0015766: Setting to allow Developers to change due date but not update an issue | ||||
Description | At the moment $g_update_bug_threshold overrides $g_due_date_update_threshold. We would like to continue to prevent Developers from updating a bug, and keep $g_update_bug_threshold set to MANAGER. However we also want to allow Developers to modify the Due Date. In some situations this would help them to set throughput targets and show likely completion dates to Reporters. For this we would set $g_due_date_update_threshold = DEVELOPER The overide currently prevents this situation. Our feature request is to make this possible. | ||||
Tags | No tags attached. | ||||
related to | 0005381 | new | more flexible group/role/profile/permission management |
This would require a new access checking system. Not too hard to implement, but quite hard to implement the upgrade from older versions. |
|
For other discussion see http://mantisbt.org/forums/viewtopic.php?f=3&t=21300 This is still an issue for us. It is almost the only thing that Mantis lets us down with. How could we promote it? |
|
It's a quite unusual workflow that developers should not be allowed to update issue details but should be able to change the due date. Another approach which would not require a new access checking system: You don't have to change any existing code of MantisBT to get it. |
|
This keeps coming up with my major client. They love Mantis and use it for many purposes, including internal ordering of services like maintenance. They want the Developer to be able to edit the Due Date to show an estimated delivery time for the service, but not to be able to change the order details. We'd like to hire a programmer to write this function and of course we'd share it with the Mantis community (you already know my agenda for promoting the use of Mantis for business issues). Atrol, could you give me just a little more explanation of the function you suggested, enough to be able to brief a programmer? Also if you could recommend someone we'd be happy to hear of them. Otherwise there seem to be people in freelancer.com who can do this stuff. |
|
I recommend to write to the mantisbt-dev and/or mantisbt-help mailing list. Maybe one of the core developers is interested. |
|
Not sure if you are referring to the implementation of a new access checking system or the quick solution with the custom function here. If the former, please note that it would be a non-negligible effort to design and then write such a specification, especially if the programmer in question is not familiar with Mantis. |
|
Not sure if you are referring to the new access checking system or the custom function here. If the former, it would already be a non-negligible effort to write such a specification, especially if the programmer in question is not familiar with Mantis. |
|
Degrad - If the quick custom function would work for us then that is all we need. I don't have a real understanding about how it would operate. Thanks for the contact, Atrol. I'll try them, but I'm still not sure how to specify the function. Could you tell me just a little more so I can get it? I do understand the access checking idea OK. |
|
David, To get you started:
[1] http://www.mantisbt.org/docs/master-1.2.x/en/administration_guide/admin.customize.customfuncs.html |
|