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

[Gabriel Bodard]

No, me either. I've been fiddling with the settings in the EpiDoc set 
(since I'm not an admin in TEI), and can't see any way to change these 
features. Will keep experimenting.

On 2013-06-18 16:52, James Cummings wrote:
> I've not found any way to change any of these aspects sadly.
>
> Happy to be corrected,
>
> James
>
>
>
> --
> Dr James Cummings, Academic IT Services, University of Oxford
>
>
>
> -------- Original message --------
> From: Gabriel Bodard <gabriel.bodard at kcl.ac.uk>
> Date: 2013/06/18 16:50 (GMT+00:00)
> To: tei-council at lists.village.Virginia.EDU
> Subject: Re: [tei-council] SF: Allura Tickets 'Priority'.
>
>
> I can sort of see Martin's point, yes. If at least the default number of
> comments visible were higher than ten (say 30, or 50) that would be a
> lot easier.
>
> On 2013-06-18 16:48, Martin Holmes wrote:
>> I'm not sure about this. It is annoying to have to page to the end of
>> the ticket, and sometimes I add a comment based on the first page,
>> forgetting there's more, but I'm getting used to it. Reading posts in
>> reverse order is more confusing, especially if you're new to the ticket
>> and it's a long one.
>>
>> On 13-06-18 03:39 AM, Lou Burnard wrote:
>>> This reminds me to ask whether anyone shares my feeling that it would be
>>> more helpful to see ticket comments in reverse chronological  order,
>>> i.e. with the most recent comment following the initial ticket text? Of
>>> course I don't know whether that's even do-able, but if it is, I'd find
>>> it a time saver, especially for tickets where the flow of comments is
>>> --shall we say-- somewhat meandering.
>>>
>>>
>>> On 17/06/13 14:28, 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
>>>>
>>>
>>
>
> --
> Dr Gabriel BODARD
> Researcher in Digital Epigraphy
>
> Digital Humanities
> King's College London
> Boris Karloff Building
> 26-29 Drury Lane
> London WC2B 5RL
>
> T: +44 (0)20 7848 1388
> E: gabriel.bodard at kcl.ac.uk
>
> http://www.digitalclassicist.org/
> http://www.currentepigraphy.org/
>
> --
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>
> PLEASE NOTE: postings to this list are publicly archived

-- 
Dr Gabriel BODARD
Researcher in Digital Epigraphy

Digital Humanities
King's College London
Boris Karloff Building
26-29 Drury Lane
London WC2B 5RL

T: +44 (0)20 7848 1388
E: gabriel.bodard at kcl.ac.uk

http://www.digitalclassicist.org/
http://www.currentepigraphy.org/