> On Oct 14, 2025, at 17:35, Jim DeLaHunt <[email protected]> wrote: > > On 2025-10-14 15:58, John Ralls wrote: > >>> On Oct 14, 2025, at 2:59 PM, Jim DeLaHunt <[email protected]> wrote: >>> >>> Hello, developers: >>> >>> I would appreciate it if user <[email protected]> could be given enough >>> access permissions on <https://bugs.gnucash.org/> to be able to edit bug >>> reports. Specifically, I would like to be able to change which component a >>> bug is labelled with, and mark that one bug is dependent on another bug. >>> From reading the docs[1] that might mean granting me "editbugs" permission. >>> But maybe the permissions list on this Bugzilla instance is different from >>> the docs. >>> >>> This arises specifically out of a gnucash-users discussion[2] about a >>> request for enhancement about reports[3] which is labelled with "Component: >>> General". I am inclined to fix such details if I am given access to. >>> >>> For now, I will post comments in the bugs describing the changes I would >>> like to see. >> Jim, >> >> Sorry, no. The edit_bugs privilege offers too many opportunities for abuse >> for us to allow non core team members to have it. Unfortunately BZ offers no >> way to create a per-field privilege. >> >> Referring to bugs in comments is actually the best way to connect them in >> BZ: The See Also field is easily (and often) ignored and provides no way of >> explaining how it might be relevant. The developers don’t use Depends on or >> Blocks for managing bugs so there’s not much point in setting them. (The >> idea behind them is that if bug F depends on A and C then A and C block F: >> You must resolve A and C before you can resolve F. As far as I know there’s >> nothing in BZ that actually enforces it.) >> >> Regards, >> John Ralls > > OK, understood. I'll stop asking for changes to See Also, Depends on, or > Block entries. > > Could someone with the appropriate access please consider the requests I made > to change Component: from General to Reports, and Importance from Ordinary to > Enhancement, for the reports-related enhancement requests I just commented in? >
Jim, I’ve already responded on the bugs. Regards, John Ralls _______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
