Note: this page is for developers and other QA people that manage GnuCash bugs in bugzilla. People that simply wish to look up bugs, or report new bugs can have a look at the general Bugzilla page.
- 1 Bug overview
- 2 Notes about Fields
- 3 Stock messages
Bugzilla's browse mode provides a very handy startpage to analyse GnuCash' bugstatus. It has overviews of bugs grouped on Component, Version, Severity and many others and it allows to drill down in any of these overviews.
Notes about Fields
Some explanations and conventions about the meaning and usage of the bugzilla fields:
Version and Target Milestone
Bugzilla provides a "Version" field and a "Target milestone" field. Both allow you to set a GnuCash version to associate with the bug.
The "Version" field is being used for the version where the bug was spotted and reported. The "Target Milestone" shows the version when the solution will appear publicly.
If you close a bug, you shouldn't modify the "Version" field because it still contains information that we might not have in any of the other fields, as sometimes the bug might have disappeared in the current version already (which means we will probably close it as DUPLICATE or OBSOLETE).
For enhancement requests, this can be different: usually it is not necessary to know the reporter's version anymore. In that case it should be set to "git-master" as long as git-master doesn't have this feature. However, there might be exceptions to this rule, in which case we should leave the Version field to the reporter's version.
- The starting state, but after the dropping of Unconfirmed/Confirmed general an open bug.
- (devs only) work in progress, see also Assigned To and its Take button.
- NeedInfo *
- devs are waiting for answers from the reporter.
- Resolved *
- It's a feature! ;-)
- Another software component is responsible.
- Reporter did not give enough information.
- Fields with *
- Reporter can select them from state NeedInfo. SO they can not reset it to New.
See also bugzilla fields
Feel free to copy this messages into the comment when closing bugs for certain reasons that occur regularly.
When closing an old bug as OBSOLETE
Thank you for taking the time to report this bug. However, you are using a version that is too old and not supported anymore. The GnuCash developers are no longer working on that version, so either this bug has already been fixed or unfortunately there will not be any bug fixes for the version that you use. The current stable version of gnucash is 2.6.16.
In the (hopefully unlikely) case you discover the same bug in the very latest stable version, do not hesitate to REOPEN it again. Also, feel free to file other bugs or enhancement requests that you find. Thank you very much!
When refusing an enhancement request as WONTFIX or setting priority=low
Thank you for taking the time to explain your enhancement request.
The described enhancement is a good proposal and would be an advantage for the software. However, as a volunteer-driven project with limited resources, the GnuCash developers have their own priorities about the features which are most likely being worked on in the near future. In that sense, the current GnuCash developers decided not to work on your proposed feature in the next 4-6 months. In case you would like to have this feature implemented in any case, you have the following option: 1. Start to program in gnucash yourself - see http://wiki.gnucash.org/wiki/Development . 2. Convince someone who is not yet part of the GnuCash team to join the team and implement your feature. 3. Pay some of the GnuCash developers to implement your feature - ask on the mailing list firstname.lastname@example.org in that case. Thank you very much.
Feel free to file other bugs or enhancement requests that you find, though.
For explaining why we ask questions even though the original report might be very old
Thanks a lot for your feedback. You are right, it was not nice from gnucash to not reply to your initial report for quite some time. We are very sorry for that. However, at the sporadic occasions when some of us check *all* currently open bugreports (even though this part of gnucash used to be in someone else's responsibility) we only have the choice to either continue not to reply, or add a reply even though the original report is already several months old (or years). In your case, we have decided it is better to reply late than not to reply at all. Thank you very much for bearing the imponderables of a large volunteer project such as ours.