Just a note. For now I haven't protected this Development Priority
field but it's expected only committers are allowed to change it.
Even more I'm conducting surveys with other XWiki developers and
XPertNet customer project teams to understand better everyone's needs,
representing the community myself during these meetings. I'm updating
the jira fields only when we reach a consensus on what's important. To
be honest I wasn't even sure (and I'm still unsure) we should make
this custom field visible since it's mostly geared towards committers
who are part of the XPertNet company (currently the biggest
contributor to XWiki - Would love that the community becomes the
biggest contributor though ;)). All other committers and contributors
are of course free to work on whatever they want. However I thought it
would be nice to show to everyone what XPertNet is considering
important.
The goal is to review all JIRA issues and categorize them into the 3
priorities and then for each version of XE assign "High" priority
issues to XPertNet committers.
Again, if you think something is not right please comment in a jira
issue but please for now don't modify directly the Development
Priority field. I'd like to experiment more with it before we can
declare that it works and that this is a good way of working.
I'll try to configure JIRA so that only committers can modify this
field.
Let me now if you have questions or any idea on how to improve this.
Thanks
-Vincent
On Jun 17, 2008, at 4:37 PM, Vincent Massol wrote:
Hi everyone,
Just to let you know that I've taken the liberty of adding a new
custom field in JIRA for Core called "Development Priority" with 3
values: low, medium and high. The idea is to categorize all our jira
issues with this field in order to prioritize our efforts. Note that
we're not using the existing Priority field since that field
represents the priority from the user's point of view.
Thus you're going to see lots of issue notifications coming in...
sorry about that.
If you don't agree about a given priority let us know as a comment in
the issue. Note that the priorities are global, i.e. compared with
other existing jira issues and not absolute.
Thanks
-Vincent