Open main menu

Gramps β

Changes

Using the bug tracker

1,158 bytes added, 00:13, 18 October 2025
Filling out the page
* 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.<ul><li> * A solution or workaround might already exist in another bug report or in the forums.</li><li>* If you connot cannot find anything resembling your issue, ask about it in one of the forums. The community will help you solve or isolate the problem.</li></ul> * 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.}}
==Report a bug==
Due to periodic SPAMbot activity, New Account requests might require human pre-approval. Be aware that this means that it might take up to 12 hours before a confirmation email is sent when creating a user account. Only after clicking on the link in the confirmation email can you submit bugs. Your email address will be handled confidentially.
{{-}}
====How Do I Change My Profile Picture on MantisBT====
MantisBT (the open source issue tracker used by the Gramps project) automatically uses your [https://gravatar.com/ Gravatar service profile] based on your registered email address.
{{-}}
*The '''Gramps''' project is a place for recording all issues with Gramps.
**If the issue represents a problem with functionality that has been released in a stable release or a problem with functionality that only exists in the master branch, then the issue should be filed under the Gramps project.
 
* For bug reports and feature requests relating to Gramps Web, see [https://www.grampsweb.org/help/ | Get Help - Gramps Web]
{{-}}
* Select Profile
** Gramps runs on multiple operating systems, so it's helpful important to know which operating system and version you are reporting an issue against. This is where you provide that information. MantisBT allows you store multiple profiles in your Account so that you can pick the appropriate one, which is handy if you run Gramps on different system configurations.
* Product Version
**The projects with names that look like '''Gramps x.x.X''' are where issues are reported that apply specifically to a maintenance branch (see [[Brief_introduction_to_Git#Types_of_branches|Types of Branches]]). A separate project exists for each maintenance branch.
**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.: 56.31.0 as shown on the [https://gramps-project.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 report.
{{-}}
* Use ''<code>@</code>'' before a user name to mention a person (note: user names with embedded spaces are not supported)
* Using ''<code>~</code>'' before a comment number writes a link to the comment, same as : ''<code>{url}#c{comment number}</code>''. eg: ''<code>~3</code>'' becomes [https://gramps-project.org/bugs/view.php?id=1#c3]
* To link a GitHub Pull Request in the bug tracker, use ''<code>p:gramps:nnnn: </code>'' where ''<code>nnnn </code>'' is the PR number. (This only applies to the main gramps repository, not add-ons.)* To link a GitHub Pull Request in the bug tracker, for Gramps addons-source paste the full Github link.
=== Limited HTML tags ===
* A [https://github.com/mantisbt/mantisbt/blob/55fb5721ea7d980557da484390db5c6003b63cd0/config_defaults_inc.php#L1979 limited set] of [https://www.w3schools.com/tags/ HTML tags] can be used in the text field:
[[Category:Developers/General]]
[[Category:Developers/Quality Assurance]]
[[Category:Troubleshooting]]
15,091
edits