The patch attached to the trouble ticket allows to associated effort figures (planned, real and remaining) with a bug report. Group bits can used to restrict access to this fields (no access, read-only access, read/write access). This concerns not only the bug form, but also the activities log and the mail sent out when the trouble ticket changes. The feature can be disabled in the parameter section.

I had to add fix the query form since the list of attributes displayed in the "Where the field(s)" selection list contains the *_effort fields even for users that don't have access to these fields. Look at the "Effort Figures Query Patch" for the necessary modifications.

The third patch - the Effort figures Buglist Patch - fixes problems with the effort figures attributes in the bug list: 1. The corresponding fields didn't appear in output you get when pressing the "Long Format" button. 2. The same applies to the "Change Columns" dialog.

We are currently trying to wrap up Bugzilla 2.16. We are now close enough to release time that anything that wasn't already ranked at P1 isn't going to make the cut. Thus this is being retargetted at 2.18. If you strongly disagree with this retargetting, please comment, however, be aware that we only have about 2 weeks left to review and test anything at this point, and we intend to devote this time to the remaining bugs that were designated as release blockers.

It's been a while since the last announcement. Is this feature still targeted for 2.18?

What about bug 24789? Isn't it something similar?

Yes, Andreas, you're right, it is similar to bug 24789. The one main difference I can see is, that my patch includes support for access restrictions, which is indispensable in my opinion.

This is, however, still a dupe of bug 24789 - if you want additional access controls, then please comment in that bug. *** This bug has been marked as a duplicate of 24789 ***

clearing target in DUPLICATE/WORKSFORME/INVALID/WONTFIX bugs so they'll show up as untriaged if they get reopened.