inline...

On Tue, Jun 9, 2015 at 11:29 PM, Benjamin Hindman <b...@eecs.berkeley.edu>
wrote:

> +1 This sounds great to me Marco. I love eliminating Reopened, as well as
> simplifying (constraining) other transitions. I couple of quick questions:
>
> Why does stoping progress go from In Progress back to Open instead of
> Accepted? Seems like it's still an Accepted issue just not being worked on.
>

I thought about it and it occurs to me that there are three reasons why one
would "Stop Progress":

   1. I haven't got time, and more important stuff came along (this is the
   case your question seems to imply)
   2. I looked into it, and it really doesn't seem worth/desirable to do,
   ever (covered in "Resolved - won't fix")
   3. I looked into it, and I have my doubts this may ever be desirable,
   but I'll leave it to others to decide (the current "Stop Progress)

I've added a "Pause Progress" transition (back to "Accepted") that covers
case #1 - would this work?


> Can we resolve or close something directly from Open? For example, issues
> we're never going to work on or are duplicates or already fixed, etc.
>

Sure - added.

>
> Do we need both Resolved and Closed? This has come up in the past, we tend
> to close issues after we cut a release with them, but it's kind of an extra
> step that I'm not convinced we really need to do.
>

Got rid of Closed.
As both Bens don't like it - I think it was doomed :)


>
> On Tue, Jun 9, 2015 at 2:26 PM Marco Massenzio <ma...@mesosphere.io>
> wrote:
>
> > Folks,
> >
> > Please take a look at MESOS-2806: in a nutshell, our current workflow is
> > rather convoluted and brings about a host of issues, when managing tasks'
> > status transitions (detailed in the Jira - see screenshots there).
> >
> > This is what it currently looks like:
> >
> > [image: Inline image 1]
> >
> > (spaghetti workflow? :)
> >
> > I would propose to simplify it to the following:
> >
> > [image: Inline image 2]
> >
> > I'm sure we can think up all sorts of corner cases, but I would submit
> > that simplicity would trump complexity and allow us to track progress (or
> > lack thereof) of stories/tasks/bugs in a much more punctual manner.
> >
> > Anyone against it?
> >
> > *Marco Massenzio*
> > *Distributed Systems Engineer*
> >
>

Reply via email to