The scheme was changed because the users could assign the release version.
Probably there was this change regarding closing the issues.
If you enable them to close the issues, pls make sure that they would not
be able to assign the release while closing.
The users may not be able to evaluate the re
Here's an example of an issue I reported and can't close:
https://issues.apache.org/jira/browse/MNGSITE-368
This issue isn't ready to be closed yet, but if it were I couldn't do
it. By contrast, issues I've reported in Jira against Beam have a
"Close Issue" button that is missing from issues I've
Maven is one of the few ASF projects that has a lot of separated JIRA projects,
hence we needed customized jira schemes,including our own permission scheme.
And we are responsible for it, not INFRA.
I can see the rights (cannot change them), and based on that I would expect a
reporter to be able
You should contact the INFRA team in Jira and ask them for your permissions
in Maven.
I also had similar problem like you in the beginning and i had to do it
this way.
So you should ask them whether you are already in commiter role/group.
On Wed, Nov 20, 2019 at 1:22 PM Elliotte Rusty Harold
wrot
I was reviewing the issues I've filed in the Apache Jira today. Some
of them including a number of Maven site issues are now fixed. I was
able to close my Beam issues where needed, but I don't have "Close" or
"Resolve" buttons for Maven issues. What's the protocol for clearing
these out?
--
Ellio
