I'm trying to chase down how to do this in JIRA: https://jira.atlassian.com/browse/GHS-5410
Anybody out there know JIRA and can save me the time!? On Mon, Oct 20, 2014 at 1:49 PM, Dominic Hamon <[email protected]> wrote: > Hi Ben > > Oh wow, sorry, I didn't even think to check that. > > One active sprint per project would be a reasonable assumption for JIRA to > make, but is going to make it very hard for us to work with sprints. Ie, > when you close your sprint you'll see your unfinished tickets fall into the > Twitter sprint, and vice versa. > > I don't know who to ask about this apparent limitation. > > - dominic > > On Mon, Oct 20, 2014 at 1:41 PM, Benjamin Hindman <[email protected]> > wrote: > > > Hey Dominic, > > > > I think we might be running into JIRA limitations. The Mesosphere scrum > > board was created independently of the Twitter scrum board (as in, it was > > not a copy), and yet the Twitter sprint showed up on the Mesosphere > board, > > and vice versa. If you go to the Apache Mesos Mesosphere Scrum board > you'll > > see that this is an independent board with it's own filters, but both > > sprints. > > > > Is it possible that all sprints for a project show up on all scrum boards > > for that project? Is there a way to separate these? Help us JIRA masters, > > you're our only hope! > > > > Ben. > > > > On Mon, Oct 20, 2014 at 11:45 AM, Dominic Hamon <[email protected] > > > > wrote: > > > > > Hi all > > > > > > As others (Mesosphere) start sprints, we have noticed a couple of > issues > > > with JIRA. The first is that incomplete issues will bubble down to the > > next > > > sprint, regardless of who owns it. Ie, I closed out our (Twitter) > sprint > > > and the issues went into Mesosphere's sprint. > > > > > > Similarly, I am unable to start a new sprint because there can only be > > one > > > active and Mesosphere is next up. > > > > > > My proposed solution: Mesosphere, and any other company that want to > use > > > sprints, should copy the scrum board we are using and set up sprints > > there. > > > The backlog will still be shared, and in fact the ordering of the > backlog > > > will be global between them, but the filters and everything else will > be > > > customisable per board. > > > > > > Ie, please leave the Apache Mesos Twitter Scrum board for Twitter's use > > and > > > set up your own board for your own use. > > > > > > Thanks! > > > > > > > > > -- > > > Dominic Hamon | @mrdo | Twitter > > > *There are no bad ideas; only good ideas that go horribly wrong.* > > > > > > > > > -- > Dominic Hamon | @mrdo | Twitter > *There are no bad ideas; only good ideas that go horribly wrong.* >
