BTS Instructions

From Bohemia Interactive Community
Revision as of 18:42, 28 April 2023 by Lou Montana (talk | contribs) (Text replacement - "\[ *((ftp|http)s?:\/\/[^ ]+) +([^ =]+) *\]" to "{{Link|$1|$3}}")
Jump to navigation Jump to search

Note: Guidelines for Admins


Bugs are now logged on a dedicated bug tracking system, called "Mantis".

If you encounter a bug, first make sure, that you started ArmA without any mods. You should contact the mod author, if the problem happens only with the mod.

Logging into the system


To file a bug, you need an account on the system.

  • If you have not filed a bug before, look here (dead link) for the signup process.
  • If you have previously filed a bug under the Wiki, an account under the same name will have been created already. The default password is "changeme". Log into the system with those settings, and then go to "My Account" to change your password.

Search for existing bugs


Before you file a bug, you should first check whether something similar has been submitted already.

For that you should go to the "View Issues" page, and enter a keyword into the search field (circled red on screenshot). Click on "Apply Filter", and if nothing relevant shows up, you can then go to the next step of filing a new bug.

Filing a new bug

Make sure that you you file a separate report for each independent issue (i.e. don't put two independent bugs into the same report).

Select Project


The first step is to select the project you're filing a bug for.

  • Armed Assault
  • Armed Assault Features (for Feature Requests)

This will most likely be "Armed Assault" at the moment.

If you check "Make Default", you will not have to select the project anymore, the next time you file a bug.

Select Category


Select which category the issue falls under.

Select Reproducibility


Select whether the bug appears all the time, or only occasionally, etc.

Select Severity


Leave the "Severity" at the default setting of "minor". A sysop will later assign it a proper priority status.

Select Version


Select which version of ArmA this bug appears under.

The version number is visible on your main ArmA screen, at the bottom left.

Complete Report

  • insert a description to reproduce the issue
  • it is often advisable to attach a file to the entry to clarify things:
    • pictures to demonstrate the error (e.g. LOD, misplaced vehicles,etc)
    • selfmade short missions for reproducing the error (e.g. scripting failures)
Make sure that you you file a separate report for each independent issue (i.e. don't put two independent bugs into the same report).

View after Report is filed


After the report is filed, you will see an updated listing of current bugs that should include your new report.

Update/Monitor Reports


If you wish to receive an email notification if the status of your filed bug is changed, click on the "Monitor Issue" button. By default you will receive email notifications on issues you did setup yourself or added notes to. If you want to change this behaviour, go to My Account - Preferences and configure your desired settings.

Adding notes

After the bug report is created, it is possible to annotate comments via "Add Note". For referencing other bug reports use the syntax "#<bugnumber>".


I think this is related with #1598.
This will be translated to
I think this is related with 0001598.

Status Codes

The color of each bug entry indicated its current status.

  • new (light pink): a bug that has just been filed.
  • feedback (dark pink): a discussion is going on regarding the status of this bug.
  • acknowledged (dark yellow): the bug is acknowledged as reproducible / real bug.
  • confirmed (light yellow): the bug was tested and it is ready to be fixed.
  • assigned (light purple): the bug has been assigned to a specific developer in order to be fixed.
  • resolved (light green): the bug has been fixed in the latest patch.
  • closed (gray): the bug has been fixed, and the reporter has closed the report.



The URL for this system is