On 3/23/07, Eli Carter <[EMAIL PROTECTED]> wrote:
>
> > Comments after testing:
> > - The 'set_resolution' action does not set the resolution to 'fixed'
> > by default.
>
> Ah, good point. Fixed.
>
> > Actually, when resolution is empty in a ticket, the
> > render_ticket_action_control() in api.py sets every option in the
> > resolution combo box as "selected".
>
> Hmm... I'm not seeing this. I see it not setting any as selected. Can you
> double-check and give me a detailed case where this happens?
It seems that the fix does not help.
It is easy to reproduce the problem if the above qarmt-workflow
settings are used. Just create a ticket, and then view HTML source for
the created ticket - the "resolve" action:
=====
<input type="radio" id="resolve" name="action" value="resolve" />
<label for="resolve">resolve as</label>
<select name="resolve_resolve_resolution"
id="resolve_resolve_resolution"><option
selected="selected">fixed</option><option
selected="selected">invalid</option><option
selected="selected">wontfix</option><option
selected="selected">duplicate</option><option
selected="selected">worksforme</option></select>
=====
When it is rendered in Firefox, it shows last selected item (e.g.
worksforme) by default.
> > Basically, I vote for inclusion of the workflow branch in 0.11 since
> > it is one of the important and constantly required features in Trac
> > IMHO.
>
> Thanks. :) The feedback you gave helps with that, and further testing is
> appreciated.
Although my free time is limited, I will spend some of my time for
reviewing/testing/playing with the new implementation.
Regards,
Pavel
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
