On 11/26/2014 07:40 AM, Fraser Tweedale wrote:
> On Tue, Nov 25, 2014 at 10:13:59AM +1000, Fraser Tweedale wrote:
>> On Mon, Nov 24, 2014 at 09:23:50AM +0100, Martin Kosek wrote:
>>> On 11/24/2014 08:39 AM, Fraser Tweedale wrote:
>>>> Hi all,
>>>> The precise meaning and usage of the "Needs UI design" field in Trac
>>>> is not clear to me.  It has five values:
>>>> - <blank>
>>>> - Not needed
>>>> - Review
>>>> - Consult
>>>> - Design
>>>> What is the purpose of this field and the meanings of the different
>>>> values?  And a more general question: is there a resource anywhere
>>>> that explains the various fields in the FreeIPA Trac?
>>> Hi Fraser,
>>> The addition Trac ticket metadata are usually added quite organically, as 
>>> they
>>> are needed. I am not aware of a page that would describe them. If the field 
>>> is
>>> not clear just from the description, it means it is possibly badly designed 
>>> :-)
>>> Needs UI design in particular was used to select tickets that needs, well, 
>>> UI
>>> review from UX specialist.
>>> But given it is not used on a frequent basis
>>> (https://fedorahosted.org/freeipa/query?uxd=!&uxd=!Not+needed&status=assigned&status=new&status=reopened&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component)
>>> I would personally just remove it and use keyword for this one time usage 
>>> (like
>>> "ux-required") to make tickets smaller.
>>> HTH,
>>> Martin
>> Thanks Martin, that does help.
>> I'll not remove the field just now but I will make a page on the
>> wiki about this.  There we can codify semantics of fields and common
>> tags, and indicate fields that are candidates for removal.
> I made a page on the Trac wiki for documenting these things:
> https://fedorahosted.org/freeipa/wiki/TicketFields.  It is also
> linked on the front page of the Trac.

Thanks Fraser, I documented the rest of the custom/unusual ticket fields we use
(except Temp mark which should be removed soon) and also linked the page from
the FreeIPA Trac front page.


Freeipa-devel mailing list

Reply via email to