On Tue, Mar 16, 2010 at 5:46 AM, Željko Filipin < [email protected]> wrote:
> I have bugged Patrick about Jira so much that he has decided to give me > full Jira admin access. :) > > (Patrick, if you are reading this - thanks.) > > He has already fixed the problem that reporters could not close resolved > tickets. I will take a look how to set up Watir Jira project so reporters > are notified by e-mail every time a ticket is changed. > > Is there anything else that should be done? > We made a list of what we wanted to do back in December. I'll see if I can find it. Do we still think Chrome, Firefox and Safari driver should have separate > projects (or sub-projects, it there is such a thing) in Jira? > Jira organizes issues by release. So we can't have stuff in the watir project that isn't part of a watir release. The firewatir and (ie)watir code should be in the same project (watir) because they pertain to a code base that is released together. Since the other projects are released on their own schedule, they need to be in a separate project. -- Bret Pettichord Lead Developer, Watir, www.watir.com Blog, www.io.com/~wazmo/blog Twitter, www.twitter.com/bpettichord
_______________________________________________ Wtr-development mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-development
