On Wed Feb 04 2015 at 12:03:35 PM Jesse <purplecabb...@gmail.com> wrote:
> Just create a parent jira issue for the 4.0.x release, and assign the rest > as sub-tasks. > You get a nice checklist in the parent issue, and you can easily tell when > all sub-tasks are completed. > Isn't this the way we used to do releases? > > No, that's only how we managed our release process. JIRA has versions where you can tag an issue with the version that it's affected by and the fixed version. We used to work on the release until we were out of issues that we wanted to fix for that release. That allowed some predictability, and shows up in the JIRA dashboard, and is something that we don't have now. I almost want to declare Issue Bankruptcy, toss out everything that's in there that's over 2 months old and start over, because as it is, JIRA is almost unusable for planning. > @purplecabbage > risingj.com > > On Wed, Feb 4, 2015 at 11:45 AM, Andrew Grieve <agri...@chromium.org> > wrote: > > > I'm no JIRA expert, but I seems there would be a way to use it (maybe via > > keywords) to track all issues remaining. > > I just use a Google doc for my list locally and like that it's super fast > > to make changes to. > > Maybe a shared Google Sheet would work best? e.g. | description | issue > > link | owner | status | > > > > On Wed, Feb 4, 2015 at 9:43 AM, Joe Bowser <bows...@gmail.com> wrote: > > > > > Hey > > > > > > I know that we have this bad habit of prioritizing what we do on the > > > mailing list instead of using JIRA, but when looking at JIRA today for > > > organizing the Cordova-Android 4.0.x release, I noticed that we don't > > have > > > the JIRA setup for independent platform releases. The main reason this > > is > > > a problem is that it makes planning for a sprint harder. > > > > > > For example, Andrew posted a laundry list of what he wanted to see > before > > > 4.0.0 is out. It would have been nice to just have a clear release > > > milestone with those tasks in it to quickly burn through, or at the > very > > > least look at. However, there's a bunch of extra noise to sort through. > > I > > > know that we could save a filter, but I don't know if we can make a > > filter > > > have all the same features as a release in JIRA. > > > > > > This is pretty low priority, but perhaps we should figure out how to > use > > > JIRA with the new way we're doing releases now? > > > > > > Thoughts? > > > > > > Joe > > > > > >
