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 release properly and they may not see if it was a side effect which made it working for them.
On Thu, Nov 21, 2019 at 7:40 PM Robert Scholte <[email protected]> wrote: > 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 to: > - close issues > - edit issues > - set issue security > - transition issues > - add comment > > If that doesn't match with your rights, let us know and we'll verify it. > > Robert > On 20-11-2019 14:28:36, Tibor Digana <[email protected]> wrote: > 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 > wrote: > > > 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? > > > > -- > > Elliotte Rusty Harold > > [email protected] > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
