When composing a problem (bug) report for Gramps:* Be '''''precise'''''* Be '''''clear''': '' explain how to reproduce the problem, step by step, so others can reproduce the bug, or understand the request.* Include only '''''one problem per report'''''* Include any relevant links and '''''examples''''' {{man tip|Before you create a "Bug" report...|Composing a bug report can involve a lot of research and writing effort. Save yourself from unnecessary work. * A solution or workaround might already exist in another bug report or in the forums.* If you cannot find anything resembling your issue, ask about it in one of the forums. The community will help you solve or isolate the problem.* If using an [[Previous_releases_of_Gramps|older Gramps version]], please mention that you have also tested with the current Gramps {{version}} version and that the issue is present.}}

===2. Search wiki and existing bugs===

Perhaps Sometimes the behavior being observed might seem odd, yet as-designed. So the first step is to search the wiki to see what the documented behavior is. If you're still not sure, ask the [https://forum.gramps-project.org/ Gramps community on Discourse.] If it still appears to be a bug, perhaps the bug you want to report has been submitted reported before. To check this, click on [https://gramps-project.org/bugs/view_all_bug_page.php {{man button|View Issues}}]. The top of the page is reserved for filters, which you set. Normally the default filters are just fine. Under these filters, there is a {{man label|Search}} box. Enter the terms best describing the bug, and click {{man button|Apply Filter}} to search. If you have an error message, try pasting a part of the error, to see if it is has been reported already.

**If the issue represents a problem with functionality that has been released in a stable release of codeor a problem with functionality that only exists in the master branch, then the issue should be filed under the project that corresponds to the maintenance branch for that release. For example, a bug found in Gramps 5.1.0 should be filed under the '''Gramps 5.1.0''' project.

*If the issue represents a problem with functionality that only exists in the master branchFor bug reports and feature requests relating to Gramps Web, or the problem exists in the master branch, but not any stable releases, then the issue should be filed under the '''see [https://www.grampsweb.org/help/ | Get Help - Gramps Master''' project.Web]

Try and complete all the relevant sections as well as you can and be prepared to answer follow up questions if your report needs clarification, it may help you to read the . Here's a concise guide on '''[[How to create a good bug report]]''' articlefor Gramps which will greatly increase the chances of reproducibility and thus being fixed.

**The For recording issues that '''Gramps Master'only'' project should only be used by developers and testers of the latest code. It is a place for recording issues that only apply to the master branch in Git (see [[Brief_introduction_to_Git#Types_of_branches|Types of Branches]]), use next un-released version e.g. There is only one "Gramps Master" : 6.1.0 as shown on the [https://gramps-project because there is only one master branch .org/bugs/roadmap_page.php| MantisBT Roadmap].* Addon Version** If you are reporting a bug in an third-party addon, use the [[Gramps_{{man version}}_Wiki_Manual_-_Navigation#Using_the_Addon_Manager...|'''Addon Manager''']] or [[Gramps_{{man version}}_Wiki_Manual_-_Plugin_Manager|'''Plugin Manager''']] (or even the [[Addon:Plugin Manager|Enhanced Plugin Manager - addon]]) to find the version of the addon and include it in the Git repositoryreport.

==Useful Mantis bug tracker Syntax codes== The following are useful [http://www.mantisbt.org/ Mantis MantisBT bug tracker] syntax codes you can use:

* Help the Gramps project [[Bug triage]] MantisBT.org reports providing user-oriented (''not'' admin) documentation* [https://www.mantisbt.org/bugs/view.php?id=5070 0005070]: I have written [MantisBT] quick-start documentation [.doc, .pdf, .swx] if you’re interested* [https://www.mantisbt.org/bugs/view.php?id=8939 0008939]: Lifecycle model [Visio] for a report in MantisBT