[haiku-web] Re: [haiku-admin] Re: Website

Axel Dörfler wrote:
Waldemar Kornewald <wkornew@xxxxxxx> wrote:
Simplify "resolve as" drop-down list (I hope nobody shouts at me for over-simplifying...):
* fixed
* duplicate
* deleted (and comment on *why*)

I don't like that too much - having a simple "invalid" is useful, too.

Good, I can understand that "invalid" may be useful in case someone creates bogus tickets and we want to be able to filter them out...

Only developers and admins are allowed to create tasks. Users may only create "defect" and "wish" tickets (later, we might not allow for wishes, anymore). This probably requires permissions per ticket type.

BTW could we pretty please rename all those defects to bugs? :-) 

Since you're asking so pretty nicely, of course we can! :)

Remove Severity (FYI, Priority will stay!).

How about the other way around?
I find "normal", "high" and these things less obvious than "normal", "critical", "blocker".

Oh, I should have explained in more detail. I wanted these priorities:
* blocker (MUST be fixed ASAP, mostly used for bugs)
* critical (MUST be finished for the affected milestone)
* high (important; might sometimes be moved to next milestone)
* normal (don't know exactly how important it is)
* low (nice to have; may never get done)
Is that okay? To me, major and minor sound too strange (at least in the context of priorities). BTW, priority should always be seen in the context of the assigned milestone.

Bye,
Waldemar

-----------------------------------------------------------------------
haiku-web@xxxxxxxxxxxxx - Haiku Web & Developer Support Discussion List

Other related posts: