Our trac instance is up. Please submit tickets and just go to town on it (its easy to replace). Do whatever you guys want to because I'll be re-making this site when it goes live.
https://hosted.fedoraproject.org/projects/fedora-infrastructure/
Requires your FAS identity to log in. Note we have F8 and F9 milestones. This whole system feels much simpler and much more natural for what we're doing then OTRS did. I don't have the source part setup yet but that can come.
Give honest feedback because we've had bugzilla and OTRS already in the last year or so. I want to make sure we get this one right.
-Mike
Mike McGrath wrote:
Our trac instance is up. Please submit tickets and just go to town on it (its easy to replace). Do whatever you guys want to because I'll be re-making this site when it goes live. https://hosted.fedoraproject.org/projects/fedora-infrastructure/
Requires your FAS identity to log in. Note we have F8 and F9 milestones. This whole system feels much simpler and much more natural for what we're doing then OTRS did. I don't have the source part setup yet but that can come.
Give honest feedback because we've had bugzilla and OTRS already in the last year or so. I want to make sure we get this one right.
-Mike
Concerning these milestones, I found that you need to very carefully choose those.
If you start with having tickets assigned to certain milestones, and then add a milestone to move some tickets to, or remove a milestone (long story short: IMACD milestones), there's no easy way of moving tickets to or from that milestone, you need to modify them by hand. In our case, not having set too much different milestones but moving as fast as we do, we have to delete and add milestones every now and then and change the default milestone for new tickets, just because our roadmap changes. Changing existing tickets already linked to a milestone is a PITA.
Just my 2 euro cents,
Kind regards,
Jeroen van Meeuwen -kanarip
On Jul 3, 2007, at 6:33 PM, Jeroen van Meeuwen wrote:
If you start with having tickets assigned to certain milestones, and then add a milestone to move some tickets to, or remove a milestone (long story short: IMACD milestones), there's no easy way of moving tickets to or from that milestone, you need to modify them by hand. In our case, not having set too much different milestones but moving as fast as we do, we have to delete and add milestones every now and then and change the default milestone for new tickets, just because our roadmap changes. Changing existing tickets already linked to a milestone is a PITA.
Just my 2 euro cents,
Have you checked out the BatchModify plugin? It looks like it was made to do exactly this.
http://trac-hacks.org/wiki/BatchModifyPlugin
Mike, I find it helpful in the 'Roadmap' section to list the tickets assigned to each Milestone. This can be done by adding the following to the Milestone description:
== Tickets for this Milestone ==
[[TicketQuery(Milestone=1.0)]]
You'll need to change '1.0' to be the name of your milestone, for example, 'Fedora 8'.
Anyway, I find it helpful :)
-Jeff
Jeff Sheltren wrote:
On Jul 3, 2007, at 6:33 PM, Jeroen van Meeuwen wrote:
If you start with having tickets assigned to certain milestones, and then add a milestone to move some tickets to, or remove a milestone (long story short: IMACD milestones), there's no easy way of moving tickets to or from that milestone, you need to modify them by hand. In our case, not having set too much different milestones but moving as fast as we do, we have to delete and add milestones every now and then and change the default milestone for new tickets, just because our roadmap changes. Changing existing tickets already linked to a milestone is a PITA.
Just my 2 euro cents,
Have you checked out the BatchModify plugin? It looks like it was made to do exactly this.
Oooh, nice. Shame on me for not having consulted <insert-your-favorite-search-engine-here>
Kind regards,
Jeroen van Meeuwen -kanarip
On Tue, 2007-07-03 at 17:14 -0500, Mike McGrath wrote:
Our trac instance is up. Please submit tickets and just go to town on it (its easy to replace). Do whatever you guys want to because I'll be re-making this site when it goes live.
https://hosted.fedoraproject.org/projects/fedora-infrastructure/
So far, this fits my workflow much better than otrs did. We'll have to see how it feels once non-infrastructure people start adding tickets.
-Toshio
infrastructure@lists.fedoraproject.org