16,736
edits
Changes
no edit summary
;Help the Gramps project with bug triaging.
Fixing a bug always starts with reproducing it, and many times the developer does not succeed in that. Making that possible is the aim of triage.
The bug/issue tracker for Gramps is located at the following URL: https://gramps-project.org/bugs
{{man note|Interested in volunteering|Read this page and then contact the [https://forum.gramps-project.org/ Gramps developers mailing list forum] and ask for [[#MantisBT_permissions|the ability to change bugs]]}}
==Goals of Bug Triage==
===What===
* "'''<span style="background:#C9CCC4">closed</span>'''"<br>
* "'''<span style="background:Lime">resolved</span>'''"]]
Make sure you're using the latest '''current '''{{version}}''' release of Gramps, using the master branch in [[Brief_introduction_to_Git|Git]] is usually best. From a clean install of Gramps attempt to reproduce the bug that is being reported. If you cannot reproduce the bug, post a comment as such - explaining the steps you took to reproduce the bug. If you encounter a different bug, file a new bug report for that problem if one has not been filed already.
* Read a bit of the [https://www.mantisbt.org/documentation.php documentation of MantisBT] so you know what is possible.
It would be beneficial to also run the master branch version of Gramps so as to test bugs that are in the master branch only.
* At the moment only projects Gramps 5.02, Gramps 56.1 0 and Gramps master are supported, so any bugs not closed or resolved in older versions must be resolved one way or the other:
** "'''<span style="background:Lime">resolved</span>'''" in the meantime
** does not apply anymore, state why and change the status to "'''<span style="background:#C9CCC4">closed</span>'''"
** version no longer supported ([https://en.wikipedia.org/wiki/End-of-life_%28product%29 EOL] versions), [[How_to_make_a_backup|backup your family trees]] and install and try with the new version
*** See: [[Previous_releases_of_Gramps|Previous releases of Gramps]]
** bug/problem still present, or move the bug to the correct project eg decide if it is a feature request?** too little information given, "'''<span style="background:#e3b7eb">feedback </span>'''" wanted from reporter** several issues in one bug, close it asking users to submit a single ticket per issue (or rename the bug for one issue, and ask to create new ones for the other),
** other issues...
===MantisBT permissions===
If you don't have MantisBT permissions (the ability to change bugs' status from Unconfirmed "new" to New"feedback", Fixed"acknowledged", "confirmed", "closed" or Invalid "resolved"), then feel free to ask on the [[Contact#Mailing_listsOfficial|gramps-develGramps Forum]] mailing list developers section for someone to set the status for you (eg: "Could someone set bug #{{bug|1}} to invalid "closed" please?). Once you do this enough, feel free to ask for MantisBT permissions on the same mailing listGramps Forum developers section .
==Status==
* https://gramps-project.org/bugs/summary_page.php
{{man warn|Note|Sometime that sometime in the past 4495 issues disappeared during a mantisdb MantisBT database upgrade|, to which a number of existing issues keep referring to.}} ==Issues==With MantisBT:* {{bug|0012273}} "Bugtracker" Make specific permission profile for people who are only triagers
==See also==
[[Category:Developers/Quality Assurance]]
[[Category:Developers/General]]
[[Category:Troubleshooting]]