Hi Jan,
The fields in issues in the IT have links to descriptions.
Those descriptions are different from the link you just provided.
For example, the instructions for the "Priority" field are:
Priority
Assign a level of importance in this field to help determine the
priority. This field is used by the programmers/engineers to prioritize
their work.
* P1 - Most important
[...]
I assume Rahul is a programmer/engineer and this issue is most important
to his work :)
Furthermore, the 'Vote for this issue' field has the following instruction:
Indicate the number of votes you want to log for this issue.
It also implicitly mentions "You may vote for the same bug more than
once", which Rahul did.
It says you'll have to bring it up with the Project Owner if you don't
want people to be allowed to cast multiple votes, it looks like it's
customizable.
Anyway, what I wanted to bring up is that it would be better to either
have the 'Priority' field's description link to the Wiki page you
provided, or have the Wiki page copied into the current description, so
that the rules are clear and consistent.
Every now and then I see a GF developer blast at a user regarding the
Priority setting, and I think it is totally unfair.
Regards,
Dies
Jan Luehe wrote:
> In the future, please file a P1 only when it's justified. It was
> certainly not justified in this case. I've added a link to the bug
> filing guidelines for GlassFish to the bug report, and I repeat it
> here for your and everybody else's convenience:
>
> http://wiki.glassfish.java.net/Wiki.jsp?page=PrioSeverDef
>
> In addition, casting 5 of your own votes for this non-issue seems
> like a waste.
>
> Jan