The internet is a lawless place with knowledge and sarcastic wit the pistols of this wild frontier.
Don't go out without being sufficiently armed.

~Blade

Other places

Ares (Current version: 0.B)

Ares's primary facilities have been moved elsewhere:

  • If you wish to report a bug in Ares, please proceed to its bugtracker.
  • If you'd like to request a feature, register a blueprint.
  • If you have questions or can provide answers regarding Ares's usage, visit the Q&A section.
  • Before you post a new question, you should check the FAQ, though.

Behavior

  • Mind the forum rules.
  • Due to its documentedly horrible quality, we do not offer NPatch support.


 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Changes to Bugtracker config
Author Message
Commander-in-Chief Renegade Offline
Lazy Modder
*****
Admins

Posts: 1 906
Joined: 21 Nov 2004
Reputation: 14
Post: #1
Changes to Bugtracker config
I just spent some time at the Bugtracker, and aside from updating/requesting to update a bunch of issues, I also did some configuration changes:
  • All issue-related pages show the "advanced page" by default now
  • I added a dozen platform/os-version profiles, so normal users should quickly be able to select their platform config now (might help track down OS-related problems)
  • I added Revisions #0029, #0033 and #0035 as RockPatch versions, so they can be selected as Product Versions and for Fixed in Version
  • I added a category "Reconnection Errors"
  • The Tracker now allows normal Reporters to re-open tickets, e.g. when a supposedly fixed issue isn't
  • And, last but not least, I tweaked the workflow transitions - took out some demotions², and issues cannot be closed right away anymore...they have to be "resolved" first.
If there's any trouble, just reply and bitch. LOL

Oh, and before I forget it: Due to the updating/reopening of issues, some older (much older) issues are currently higher on top than "current" issues, which might be confusing at first - nevertheless, fixing the old issues (or confirming they are fixed) is even more important than fixing the fresh bugs. If they're all fixed anyway and were just badly updated before, they'll soon be gone anyway - if not, good that I re-opened them! Wink


² e.g. an "assigned" bug cannot be re-status'd to "acknowledged" anymore...'cause if it was assigned already, it must at least have been confirmed before.

Forum Rules

(01.06.2011 05:43:25)kenosis Wrote:  Oh damn don't be disgraced again!

(25.06.2011 20:42:59)Nighthawk Wrote:  The proverbial bearded omni-bug may be dead, but the containment campaign is still being waged in the desert.
26.12.2006 06:45:37
Visit this user's website Find all posts by this user
Private VK Offline
Assembler maniac
*****
Members

Posts: 832
Joined: 10 Jun 2006
Reputation: 2
Post: #2
RE: Changes to Bugtracker config
Fantastic...
I have 40 messages in email about changing reports Unhappy
BTW, Can you add label, which reminds people, what they really should post and that?
For example wishes, bug, which appeared only once, ...

ARM forever - x86 sucks!
27.12.2006 21:57:14
Find all posts by this user
Commander-in-Chief Renegade Offline
Lazy Modder
*****
Admins

Posts: 1 906
Joined: 21 Nov 2004
Reputation: 14
Post: #3
RE: Changes to Bugtracker config
CnCVK Wrote:Fantastic...
I have 40 messages in email about changing reports Unhappy
That's what you get for forcing us to review all reports Tongue

CnCVK Wrote:BTW, Can you add label, which reminds people, what they really should post and that?
For example wishes, bug, which appeared only once, ...
All of that has always been available. Wishes/bugs can be seperated through Severity (has a "feature" setting for feature requests), the frequency of a bug's appearance can be reported through Reproducability - if it only appeared once, then it obviously needs a Reproducability setting of "unable to reproduce".

This question, however, shows that you haven't looked into the system a lot yet - which, in turn, is probably the reason why we needed to update all these reports.

Update: Since there seemed to be some confusion regarding when to set which status/resolution/severity, I sat down and wrote definitions for all of them. Of course older issues might not adhere to them, but it should bring some structure into future workflow.

Forum Rules

(01.06.2011 05:43:25)kenosis Wrote:  Oh damn don't be disgraced again!

(25.06.2011 20:42:59)Nighthawk Wrote:  The proverbial bearded omni-bug may be dead, but the containment campaign is still being waged in the desert.
28.12.2006 00:47:10
Visit this user's website Find all posts by this user




User(s) browsing this thread: 1 Guest(s)