infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Owen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-15221) Disable Closed -> Reopened Transition?
Date Sun, 08 Oct 2017 11:47:00 GMT

     [ https://issues.apache.org/jira/browse/INFRA-15221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sean Owen updated INFRA-15221:
------------------------------
    Status: Waiting for Infra  (was: Closed)

[~gmcdonald] [~gstein] per the follow-up conversation, I'm reopening this to request adding
the capability to restrict Closed -> Reopened transitions to the JIRA Committer role. See
the dev@ thread above. There was no objection, though healthy discussion about not using this
unless required. I believe we should have this option, at least, as I think it's even the
default setting for new projects?

> Disable Closed -> Reopened Transition?
> --------------------------------------
>
>                 Key: INFRA-15221
>                 URL: https://issues.apache.org/jira/browse/INFRA-15221
>             Project: Infrastructure
>          Issue Type: Task
>          Components: JIRA
>            Reporter: Sean Owen
>            Assignee: Greg Stein
>            Priority: Minor
>
> We have an occasional issue with a user submitted a JIRA that is subsequently closed
by committers, but continually reopened by a user that disagrees for whatever reason.
> Most JIRAs end in the "Resolved" state and it's useful to be able to reopen those. But
it would be useful to let project committers alone permanently close an issue.
> I think this boils down to asking to disable the Closed -> Reopened transition, if
possible, for Spark? or at least disable it for Contributors, but let Committers do it?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message