see https://qa.mandriva.com/page.cgi?id=fields.html for an example of definition

(In reply to comment #0)
> Define :
> - what the severity will be used for (and who sets it)
> - what the priority will be used for (and who sets it)

I don't get what you want to say here...

we have http://bugs.mageia.org/page.cgi?id=fields.html

webteam can enhance it too. Like ahmad i don't see what you mean exactly, can you give some more infos ?

Yes, I was not clear.

In Mandriva's bugzilla here are the values for both fields :
priority :
- low
- normal
- high
- release critical
severity : 
- Critical 	crashes, loss of data, severe memory leak
- Major 	major loss of function
- Normal 	regular issue, some loss of functionality under specific circumstances
- Minor 	minor loss of function, or other problem where easy workaround is present
- Trivial 	cosmetic problem like misspelled words or misaligned text
Enhancement 	Request for enhancement

In Mageia's bugzilla, here are the current values :
priority :
- lower
- low
- normal
- high
- higher
severity :
- blocker 	Blocks development and/or testing work
- critical 	crashes, loss of data, severe memory leak
- major 	major loss of function
- normal 	regular issue, some loss of functionality under specific circumstances
- minor 	minor loss of function, or other problem where easy workaround is present
- trivial 	cosmetic problem like misspelled words or misaligned text
- enhancement 	Request for enhancement

I think Mandriva's scheme is simpler here, especially for priority (only 3 items + the release_critical item). 
There's also an important question to answer : how to mark release critical bugs ?
=> via the release_critical priority ?
=> via the blocker severity ?

Using the priority for that (like Mandriva does) would better respect the distinction between severity and priority (as defined in http://bugs.mageia.org/page.cgi?id=fields.html):
- severity is the importance of the bug (set by bug reporters usually, sometimes changed by triage team or packagers so match best the actual bug impact)
- priority is set by the developers/packagers or product owners to prioritize their work. I can be different than severity (critical severity on a rarely used package may be given low priority). Bug reporters should not touch it (I don't know whether we should enforce that rule via a setting or not)

Yes, we'll work on the severity and the priority lists next, along with having the Severity and Priority labels visible in our bugzilla instance, this is planned (at least that is the next request I'll bug dmorgan about after having the labels visible).

I am not with or against having release_critical/release_blocker in Severity or Priority, it makes sense (to me at least) in either list. But I think we should have just one, release_blocker, this is more easy to understand.

As to who sets what, the policy in mdv changed to open bugzilla for all, i.e. anyone with an account in bugzilla can change anything regarding a bug report. This is not the case in all distros/projects, some others don't allow regular users to close bugs, set severity/priority... etc.

i added severity and priority instead of importance on our bugzilla.
and i changed the fields according to what ahmad told me.

Status: NEW => RESOLVED
Resolution: (none) => FIXED