Hi Brad, And regards to everyone else Yellow-tinted in Raleigh
У уто, 13. 12 2011. у 17:53 -0500, Brad Crittenden пише: > * Milestones can have zero or more tags, just like bug tags. > > * A new project group page <projectgroup>/+tag/<tag> will be produced > to show all items associated with the milestones tagged with <tag>. It > will look very similar to <projectgroup>+milestone/<milestone> but the > milestones will be filtered by the tag. (See attached mockup, page 1.) > > * The project group overview page will have a new section titled > "Milestones" and in it will be a text entry box with a search button. > Use of the search will take the user to the +tag page described above. > The entry box will autocomplete known tags. (See attached mockup, page > 2.) This actually sounds pretty good for our use case. When can we have it? :) FWIW, this kind of solution would make me very happy since it will solve some of our other outstanding issues, and will provide a path forward for us (eg. if we can tag something with "linaro-infrastructure" team tag at the same time, and we can get to the page for that tag as well, we'd get so much closer to the dashboards we also need - ha :). > Other considerations (not for first cut): > > * API > - projectgroup.getAllMilestonesByTag() > - projectgroup.getAllMilestoneTags() > - project.getAllMilestonesByTag() > - project.getAllMilestoneTags() These would be great to have. > * Official milestone tags per project group > - In the future it may be desirable to have official tags, analagous to > official bug tags. > - A mechanism for creating a new milestone tag and assigning it to > milestones in the constituent projects. This brings another consideration for me: who can add the tags, and who can remove them? Just maintainers/drivers? If anyone can do it, we'd be worried when we try to use them to manage our releases (which is why we are using milestones atm). > * Provide a similar <project>/+tag page and a means to navigate to it. The other thing I'd really like to see is ability to combine tags as well, i.e. <projectgroup>/+tag/2011.12/infrastructure — I understand that may have other implications (like performance and such; of course, the URL example above is nothing but an example). This does not have to be there in the first go, and we'd be interested in investing resources in allowing that if the infrastructure is such that it provides for it. Mockups also show nothing about how the tags are created, so I hope that's going to be easy enough and will fall nicely into our release management activities. Cheers, Danilo _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : launchpad-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
