Mantis

From icesus
Jump to navigation Jump to search

We use a web-based tool called Mantis for reporting bugs, typos, ideas and issues.

Mantis can be found from here:

https://naga.icesus.org/mantis/

To use Mantis, you have to create an account which you can do by clicking on the above link.

Create an user to Mantis with the same name as your Icesus character (e.g. if my Icesus character's name is Cyto, I create an account named 'cyto' to Mantis).

Once your Mantis user is created, a confirmation mail is sent to your email address.

However, as our server is not a 100% trusted email sender, some email services such as google might block our mails (some do not, e.g. outlook receives them just fine). We are working on getting our mail server into more trusted.

If the confirmation mail doesn't arrive to your inbox within a minute or so, paste this the line below to Icesus and wizards will be alerted to confirm your user account.

accounts I want my Mantis account activated.

Once you get a reply from a wizard containing your password, your account is active. Most of the time it should take just a few hours, depending on how active wizards are.

Below you will find instructions on how to create a bug reports, typo reports, idea suggestions and issues in a way that they have the best chances of getting processed and done.

All report types below require you to login to Mantis first and clicking on "report issue" as your very first thing:

Report issue.png

Creating a bug report

Tip: Think carefully whether to create tickets public or private. Rule of thumb: Any "personal issues" = it is directly between you and the game, e.g. reimbursements = private. Anything else, especially tune proposals which concern more people than just ticket creator and the game = public.

Enter issue details as follows:

  • Select Category: bug
  • Select reproducibility:
    • "always" if the bug happens each and every time you do something.
    • "sometimes" if the bug is harder to catch and happens only sometimes.
    • "random" if the bug is hard to catch; happens only randomly.
    • "have not tried" if you haven't tried reproducing the bug (if you want your bug report to be forgotten, use this)
    • "unable to reproduce" if you caught the bug once, but have not been able to catch it twice, or it is extremely hard to catch. Note that sometimes it might be just a glitch or a fluke and there might not even be a bug.
  • Select severity:
    • "trivial": doesn't matter much, almost at all, just a FYI sort of thing (if you want your bug report to be almost forgotten, use this)
    • "tweak": just a little aesthetic tune please.
    • "minor": the bug bothers a little, and mainly only you, in a very specific situation which doesn't affect gameplay or create abuse holes.
    • "major": the bug bothers you quite a lot, but mainly only you, in generic situations which can affect your gameplay and also your fellow players' gameplay.
    • "crash": you did this and game crashed. Very serious bug and almost always earns you PDF if caught by your report.
    • "block": this bug bothers you a lot and is almost ruining your gameplay experience (almost because if it did, you wouldn't be reporting bugs right?). These bugs will be prioritized to the highest priority, but don't use this severity in vain. As in if there are people who are reporting only blocker bugs, and others are not bothered by it at all, there might be a problem with the people who do that, not in the game.
    • "feature": please do not use this severity in bug reporting. Only wizards can set this on a bug. It means it has been screened by a wizard and he has concluded that it is not a bug, rather a feature.
    • "text": please do not use this severity in bug reporting at all.
  • Select priority: Please do not set priority on bugs. Leave this to wizards who screen the bugs and then prioritize them in order of fixing.
  • Assign to: You shouldn't set this. Leave this to wizards who know who is responsible for the part of the code that is bugging.
  • Summary: Write a short one-liner about the bug, which is search friendly (meaning other players who ponder about the same issue can search for these generic words and find if a ticket on it already exists).
  • Description: Write as long description about the bug as you like. Don't write how you managed to make it happen (it comes next). Write what the bug is about.
  • Steps to reproduce: Here, write how you managed to come across the bug. Feel free to include log snippets. If the log is going to be HUGE, please use "upload file" a little more down.
  • Additional information: Anything else you would like to report about this which isn't quite possible using the above fields.
  • View status: Do you want this issue to be handled privately, or do you want it to be seen by everyone. Latter is preferred as it prevents creation of duplicate issues.

Creating a typo report

Enter issue details as follows:

  • Select Category: typo
  • Select reproducibility:
    • "always" if the typo happens each and every time you do something.
    • "sometimes" if the typo is harder to catch and happens only sometimes.
    • "random" if the typo is hard to catch; happens only randomly.
    • "have not tried" if you haven't tried reproducing the typo (if you want your typo report to be forgotten, use this)
    • "unable to reproduce" if you caught the typo once, but have not been able to catch it twice, or it is extremely hard to catch. Note that sometimes it might be just a glitch or a fluke and there might not even be a bug.
  • Select severity: text
  • Select priority: Please do not set priority on typos. Leave this to wizards who screen the typos and then prioritize them in order of fixing.
  • Assign to: You shouldn't set this. Leave this to wizards who know who is responsible for the part of the code that contains the typo.
  • Summary: Write a short one-liner about the typo, which is search friendly (meaning other players who ponder about the same typo can search for these generic words and find if a ticket on it already exists).
  • Description: Write as long description about the typo as you like. Don't write how you managed to make it happen (it comes next). Write what the typo is about.
  • Steps to reproduce: Here, write how you managed to come across the typo. Feel free to include log snippets. If the log is going to be HUGE, please use "upload file" a little more down.
  • Additional information: Anything else you would like to report about this which isn't quite possible using the above fields.
  • View status: Do you want this issue to be handled privately, or do you want it to be seen by everyone. Latter is preferred as it prevents creation of duplicate issues.

Creating a new idea

Enter issue details as follows:

  • Select Category: idea
  • Select reproducibility: Choose any option you like, it doesn't matter.
  • Select severity: How important do you think this feature would be for the whole of Icesus? Use same guidelines as in bug reporting.
  • Select priority: Please do not set priority on ideas. Leave this to wizards who screen the ideas and then prioritize them in order of implementation.
  • Assign to: You shouldn't set this. Leave this to wizards who agree who is going to do this feature.
  • Summary: Write a short one-liner about the idea, which is search friendly (meaning other players who ponder about the same idea can search for these generic words and find if a ticket on it already exists).
  • Description: Write as long description about the idea as you like. Don't write about technical aspects of the idea, just what the idea is about.
  • Steps to reproduce: Here, write more technical description of the idea. Feel free to include logs and auxiliary files to help get the image. If the idea description is going to be HUGE, please use "upload file" a little more down.
  • Additional information: Anything else you would like to report about this which isn't quite possible using the above fields.
  • View status: Do you want this issue to be handled privately, or do you want it to be seen by everyone. Latter is preferred as it prevents creation of duplicate issues.

Creating an issue

Issue is a formal proceeding for approaching the administration when you have encountered a situation (issue) in which you feel the administration should intervene. These situations occur most commonly in regard to player killing (see 'help player killing') and losing equipment (see 'help reimburse').

There are several requirements an issue-report must fulfill to be qualified for investigation by the administration. The issue-report must include at least the following information concerning the arisen situation:

  1. exact time, duration and location
  2. names of all relevant characters
  3. detailed description of the situation and the contribution of each relevant character
  4. quotations of all relevant discussions relating to the situation
  5. a claim for reimbursement and/or retribution
  6. legal basis for the claim (e.g. references to the relevant rules or help files)

If the issue fails to meet the aforementioned requirements, the administration may dismiss the issue without further investigating the facts and circumstances of the case.

Issues directed at other characters ("issue add <player>") will be forwarded to the concerned defendant. The defendant shall provide a thorough statement of defence. The statement must include well-founded rebuttal of all claims put forth by the complainant. Failing to provide such defence the administration may give judgment without further investigating the facts and circumstances and thus constitute judgment on the issue-report alone.

Enter issue details as follows:

  • Select Category: issue
  • Select reproducibility: Choose any you like, doesn't matter
  • Select severity:
    • "trivial": doesn't matter much, almost at all, just a FYI sort of thing (if you want your issue report to be almost forgotten, use this)
    • "tweak": maybe just a reminder is enough
    • "minor": there was an infraction or violation of rules which should come with sanctions, but not too severe.
    • "major": there was a major infraction or violation of rules which should come with major sanctions. Robotting and multiplaying fall here. Chance of earning PDF here.
    • "crash": please do not use this severity in reporting issues.
    • "block": this is about an abuse of a bug or some infringement of great magnitude, which has brought monetary or other rewards to a player or a group of players (even worse). This is a major accusation and will be dealt with the most meticulous investigation and harshest penalties. This will always bring PDF to the reporter, if the issue is deemed valid.
    • "feature": please do not use this severity in issue reporting.
    • "text": please do not use this severity in issue reporting.
  • Select priority: Please do not set priority on issues. Leave this to wizards who screen the issues and then prioritize them in order of prosecution.
  • Assign to: You shouldn't set this. Leave this to wizards who know who is the best person to handle this.
  • Summary: Write a short one-liner about the issue, which is search friendly (meaning other players who ponder about the same issue can search for these generic words and find if a ticket on it already exists).
  • Description: Write as long description about the issue as you like, according to the description of what issue means above. Remember, you need all six points mentioned in that description to have an issue.
  • Steps to reproduce: Here, write how the infraction happened technically and how you managed to catch it. Feel free to include log snippets. If the log is going to be HUGE, please use "upload file" a little more down.
  • Additional information: Anything else you would like to report about this which isn't quite possible using the above fields.
  • View status: Do you want this issue to be handled privately, or do you want it to be seen by everyone. Latter is preferred as it prevents creation of duplicate issues, but understanding the sensitivity of some cases private is OK as well.