Suggestions to retag bug reports
asked 2015-09-17 11:15:33 +0300
Currently, there is no official rule on tagging the bug reports posted on TJC, but it has become a common way to add a tag bug and a version number tag, for example 1.1.7.28, representing the Sailfish OS release on which the bug was encountered.
Version number tagging has been used especially on releases which are not yet public for everybody. This seems useful, as it helps to filter out bug reports on unreleased software, or filter in bug reports for only certain version.
However, the tagging is not working the best way it might do. Regarding version numbering, the current reports can be shared roughly into four different categories:
- without any version number tag
- with a version number tag representing the first version the bug was located on
- with a version number tag (retagged) with the latest version they are still encountered on
- with several version number tags (minority), repsententing versions they are encountered on
In this question, I'm asking for suggestions for the best practice in bug report tagging. You don't need to hold on only to the version numbering, but you can suggest any practical way to tag bug reports, even adding new kind of tags into your suggestion. Let's vote the best suggestions up, and see if we can do something for TJC to work even better.
EDIT: Just checked some statistics how the current "routine" is working. Since the latest Early Access version was rolled out, there's been 150 bug -tagged reports. 82 * 1.1.9.2812 * 1.1.7.28 56 * w/o version. Me thinks this check gives a reason to actually find another way, so looking forward for your suggestions. The current way is not working.
Note: This question is not about if bug reporting should be done somewhere else. This is to find the best practice while it's still done here on TJC.