Changes

From Gramps

Using the bug tracker

28 bytes removed, 23:15, 23 September 2020
3. Submit new bug: merge the two
Click on one of the {{man label|Report Issue}} buttons, and enter the required information, see below on how to select the project to which the bug belongs. Be verbose, the developers are bad at mind reading. We shall mercilessly close the bugs which have no meaningful information at all, such as #{{bug|7126}}. Do not forget to list the Gramps version you are using. You can check this in Gramps by clicking in the Gramps program the Help menu, option About.
{{-}}
==== Projects How to proceed ====
[[File:Dropdown-Choose-Project-GrampsBugtracker.png|thumb|right|450px|Choose Project - selection list]]
On The first step in submitting an issue on the tracker is to determine which project it belongs to on the issue tracker from the '''Select Project''' box, use the '''Choose Project''' drop down list to select the "project" for the bugs. "Projects" are a way to categorize issues. There are two types of projects in the issue tracker, '''Feature Requests''' and '''Gramps''':
#The '''Feature Requests''' project is a place for recording requests for new features.
#The '''Gramps''' project is a place for recording all issues with Gramps.
{{-}}
==== How to proceed ====
The first step in submitting an issue on the tracker is to determine which project it belongs to.
 
*If the issue represents functionality that does not currently exist in Gramps, then the issue should be filed under the '''Feature Requests''' project.
#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 of code, 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.
301
edits

Navigation menu