Hi
We're using FogBugz to track project tasks as well as issues. We would like to make the due-date field non-editable, while still allowing developers to change the rest of the ticket.
Is this possible?
Thanks
Gary Broughton
|
2
|
Hi We're using FogBugz to track project tasks as well as issues. We would like to make the due-date field non-editable, while still allowing developers to change the rest of the ticket. Is this possible? Thanks |
|||
|
|
|
1
|
One way to do this would be to write a small snippet of JavaScript, using the Bugmonkey plugin, to disable the field. You would want to make sure to only have the field disabled for editing cases, and not for new cases, so that you can initially enter a due date. This is by no means a sufficient script, but it should get you on your way (Untested, but at least to disable the fields whenever they are visible on page-load):
I would caution against this, however, because you will probably run into a situation where you need to change the due date on a field, perhaps because it was entered incorrectly when the case was created. If you disable editing, then you would have to turn off the script to fix the mistake. Also, since all changes to a case are logged, you can easily see where some one has messed with the due date. So, rather than enforce a restriction on your developers, perhaps try simply asking them not to change it first and see if that works. It would be much less hassle, and less complicated, to simply ask the developers not to change the due dates than to get in their way if they think they want to do something. Developers are a crafty bunch...if you give them a problem, they will work REALLY hard to get around it, especially if they think someone is getting in their way. |
|||
|
|
|
0
|
You could also write a plugin that checks for changes to certain fields. If they're changed by non-admins (or project admins, etc), it would then edit the case again and switch it back and tell the user why. (plugins cannot currently abort the commit process and prevent an edit) This same plugin could also add the JS that cdeszaq mentioned you could put in via Bugmonkey. |
||
|
|