Please don't re-open issues (unless for the very specific case in which a patch gets committed and then turns out to either be insufficient to meet requirements and/or buggy).
It's much better to instead create a new one and reference the original one (you can even "Link" to it, or just reference it in the comment). (there's also a peculiar Jira issue in which the "Resolved" state doesn't get cleared once one moves it back in "open" or "in progress" and the issue continues to appear struck out in lists, sprints, backlog, etc. confusing the obsessives like me :)). Thanks! *Marco Massenzio* *Distributed Systems Engineer* On Wed, Jul 29, 2015 at 8:30 AM, James DeFelice <james.defel...@gmail.com> wrote: > Yep I was logged in > > On Wed, Jul 29, 2015 at 11:21 AM, Alex Rukletsov <a...@mesosphere.com> > wrote: > > > That's weird, because AFAIK I'm a regular contributor without any > elevated > > rights. > > > > Just to make sure and exclude this option: were you logged in? > > > > On Wed, Jul 29, 2015 at 5:06 PM, James DeFelice < > james.defel...@gmail.com> > > wrote: > > > > > Thanks. I probably don't have ops. How do I get them? > > > > > > On Wed, Jul 29, 2015 at 10:57 AM, Alex Rukletsov <a...@mesosphere.com> > > > wrote: > > > > > > > It looks like it worked for me: I was able to re-open it. > > > > > > > > On Wed, Jul 29, 2015 at 4:51 PM, James DeFelice < > > > james.defel...@gmail.com> > > > > wrote: > > > > > > > > > I'd like to re-open > https://issues.apache.org/jira/browse/MESOS-349 > > > for > > > > > discussion. I have a very specific use case in mind that the file > > > system > > > > > isolator will not solve for me. > > > > > > > > > > JIRA won't let me re-open this -- possibly related to the recent > > > workflow > > > > > changes? > > > > > > > > > > > > > > > > > > > > > -- > > > James DeFelice > > > 585.241.9488 (voice) > > > 650.649.6071 (fax) > > > > > > > > > -- > James DeFelice > 585.241.9488 (voice) > 650.649.6071 (fax) >
