BMSBugs: A public third party BMS bugtracker
-
we probably didnt need bugtracking for obsolete versions at this stage.
Yup
So 4.35 is out of the scope then -
Ah, its rapid development indeed when the ālatest-stableā commit is also marked āobsoleteā.
-
One of the important things is the ability of the user to think about searching before reporting.
-
One of the important things is the ability of the user to think about searching before reporting.
There is a feature of GitHub Issues, which I am missing currently with this setup, where as you type in the title of a new report, the page suggests other issues with similar titles, to try avoid duplicate reports. I will have a look to see if this is something that can be implemented within MantisBT.
Edit: seems its been a requested feature of this bug tracking software since 2009.
-
There is a feature of GitHub Issues, which I am missing currently with this setup, where as you type in the title of a new report, the page suggests other issues with similar titles, to try avoid duplicate reports. I will have a look to see if this is something that can be implemented within MantisBT.
as in my RL Projects we are mainly using either JIRA or Gitlab for issue tracking, one of the most used function is to relate entries to each other eithr by reference or mark them as duplicate
-
as in my RL Projects we are mainly using either JIRA or Gitlab for issue tracking, one of the most used function is to relate entries to each other eithr by reference or mark them as duplicate
You can do this. What I was wanting was to have an automatic suggestion pop up to the user before they create an issue, about issues which might be similar to their issue.
You can mark an issue as a duplicate, and it will link to the original issue much as you would see in GitLab (cant comment on Jira as Ive not actually used it). Ive not used Mantis before so Im learning too. Was going to be bugzilla (which I am far more familiar with), but Mantis was a one click install on my web hosting, and bugzilla was going to be, while relatively straightforward, not as straightforward as a one click install.
-
Hello,
this is an excellent initiative!
I was really thinking that was missing.Also, will this also be the place where to send crash reports?
(Iām having a lot of them since 4.35 ) -
ā¦JIRAā¦shudderā¦
-
Hello,
this is an excellent initiative!
I was really thinking that was missing.Also, will this also be the place where to send crash reports?
(Iām having a lot of them since 4.35 )You can upload attachments to a bug or crash report if you log in. There might be a size limit though.
-
Updated first post with Bug Report Checklist for filing an effective bug report. As per the updated first post, please file issues as ānormalā priority, unless you are filing in your capacity as a BMS team member. As a public tracker, we can make determinations on bug severity, but not on bug priority. Filing a bug as high or low priority will be taken as a suggestion at best, and in any event will not enforce any particular order of viewing by the dev team.
Severity: How significantly the bug impacts your ability to use the software as a combat flight sim generally.
Priority: How important it is to the team to fix the bug.
Very much the case that deciding priority is out of scope for non-team members.
-
Is it wanted that a BUG report is added here in the forum as well as in the BMS BUG page at the same time? Or that page is more for the devs?
I saw someone added my CTD report, but files are missing. -
The BMS Bugs page is for the community. Its for the community, and also for the BMS team.
I guess the question of āwantedā depends who you ask. I want bugs to be reported on the BMS Bugs page. The intent is very much that it will replace reporting bugs here on the forum, and that it will be much easier to search, sort and identify public issues with BMS, as well as cutting down on the content needing to be moderated on the forum. Ideally, it will also promote communication on issues between the team and the community.
As its not official, I cant tell you what is wanted by the team. What I can say is, please dont avoid making a bug report on BMS Bugs, the page is very much not ājust for devsā but for everyone.
I added your CTD report, but Id thought Id added links to the files. Which files were missing?
-
Ok. I understand. I will then double the reports here and there. I just want to avoid that a āpotentialā bug is oversaw because it was posted here/there.
Just saw the links on the additional information. All good. Good stuff, Blue3wolf!
-
Hi folks,
Iāve added two more issues (planes spawn in the same spot in MP during RAMP and players seeing the āEnd missionā dialog mid-flight in 3d when somebody disconnects).
These are basically reminders for now while more data is being gathered, so if youāre seeing these issues as well please add and triaging info to the bug report:
āPlanes spawning in MP in the same spotā:
https://bmsbugs.blu3wolf.com/view.php?id=14āEnd of Missionā MP dialog:
https://bmsbugs.blu3wolf.com/view.php?id=15Thanks & all the best,
Uwe
-
Updated first post to clarify Resolved issues and Closed issues. In short, resolved issues have a fix, but that fix is not yet public. Issues are closed when their fix is released.
If you are searching to see if your bug has been reported, you should not ignore issues which have been resolved, as those issues will still be present in your version of BMS.
-
At first I thought it wouldnāt be a good idea to add another bug tracker, but I was wrong.
Thumbs up, it is a great idea. Thanks to Blu3wolf! -
Enabled display of verify and feedback boxes. Effect is only visible if you are logged in, and it adds boxes to the My View page: https://bmsbugs.blu3wolf.com/
Specifically, āAwaiting Confirmation of Resolution from Meā and āAwaiting Feedback from Meā, with each box containing relevant issues. If a bug is marked as āresolvedā by a dev, your issue will be listed under āawaiting confirmation of resolutionā. You can then close the issue once you have confirmed the issue is resolved in the next BMS release. If a bug is marked as āfeedbackā, your issue will be listed under āawaiting feedbackā, with a comment on the issue explaining the further information required to clarify the issue.
Thanks again to everyone who has reported bugs, or helped resolve them. It is very cool seeing the list of bugs fixed in next version, grow longer and longer!
-
How can a Issue can be assigned to a Dev/Corrector ?
-
Hi TOPOLO,
Its a feature of what your account permissions are. I Hawk, Bad Boy, DeeJay and Mav have accounts with āmanagerā permissions and can assign issues to any account which is a ādeveloperā or āmanagerā. They can also add new user accounts to the project as ādeveloperā or āmanagerā.
If you are not logged in, or if you are logged in with āreporterā permissions (which is the default), you can report issues, but not assign them to anyone in particular.
It is also possible to set issues which are reported in a particular category, as automatically being assigned to a specific developer, but so far as I know this hasnt been done.
EDIT: TOPOLO, your account should now have permissions set to assign issues to developers. Thanks!
-
Thanks a lot !