spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sean Owen <>
Subject Re: Disabling Closed -> Reopened transition for non-committers
Date Thu, 05 Oct 2017 02:51:37 GMT
Although I assume we could get an account suspended if it started opening
spam issues, yes we default to letting anyone open issues, and potentially
abusing it. That much is the right default and I don't see any policy tweak
that stops that.

I see several INFRA tickets asking to *allow* the Closed -> Reopened
transition, which suggests it's not the default.

I'm accustomed to Closed being a final state that nobody can reopen as a
matter of workflow -- the idea being that anything else should be a new
discussion if the current issue was deemed formally done.

Spark pretty much leaves all issues in "Resolved" status which can still be
reopened, and I think that's right. Although I'd like to limit all
reopening to committers, it isn't that important.

Being able to move a JIRA to Closed permanently seems useful, as it doesn't
interfere with any normal workflow, doesn't actually prevent a new issue
from succeeding it in normal usage, and gives another tool to limit a
specific kind of abuse.

On Thu, Oct 5, 2017 at 3:28 AM Dongjoon Hyun <>

> It can stop reopening, but new JIRA issues with duplicate content will be
> created intentionally instead.
> Is that policy (privileged reopening) used in other Apache communities for
> that purpose?
> On Wed, Oct 4, 2017 at 7:06 PM, Sean Owen <> wrote:
>> We have this problem occasionally, where a disgruntled user continually
>> reopens an issue after it's closed.
>> (Feel free to comment on this one if anyone disagrees)
>> Regardless of that particular JIRA, I'd like to disable to Closed ->
>> Reopened transition for non-committers:

View raw message