[tei-council] SF: Allura Tickets 'Priority'.

[Kevin Hawkins]

I don't object; however, I'd like to point out something I've just noticed.

While anyone can add a comment to a ticket in Allura, you can only 
change who it's assigned to or its status by "editing" the ticket.  When 
you do this, it allows you to edit many fields, including the priority. 
  Unfortunately, the edit screen always sets the priority to "1(low)" 
when you go to this edit screen.  I suspect this is a bug in Allura, but 
it's such a huge bug that I wonder whether we in fact have "1(low)" set 
as the default priority or something -- that is, maybe this is something 
we can fix before we try to get the attention of the folks at SourceForge.

--K.

On 6/17/13 9:28 AM, James Cummings wrote:
>
> Hiya,
>
> In response to one of my actions I've investigated and with a bit
> of fiddling changed the priority field to be:  "1(low) 2 3 4
> *"5(default)" 6 7 8 "9(high)" which means going forward the '1'
> items will be '1(low)', etc. this is a bit awkward but better
> than just a set of unglossed numbers.
>
> This is a 'select' field, the other options for ticket metadata
> fields are:
> 'text', 'number', 'boolean', 'milestone' and 'user', which aren't
> as useful, I think, for this field.
>
> Let me know if anyone objects strongly to that, because I can
> revert it, otherwise new tickets will start using these glossed
> numbers.
>
> -James
>