Unable to close any issue even allowed reporters from configuration.

General discussion of Mantis.

Moderators: Developer, Contributor

Post Reply
haseebraza
Posts: 26
Joined: Mar 07, 2019 5:02 pm

Unable to close any issue even allowed reporters from configuration.

Post by haseebraza »

There is no option in release 2.5 for any issue to "closed".
Resolution "fixed" is not allowed for status "assigned".

cas
Posts: 806
Joined: Mar 11, 2006 11:08 am
Contact:

Re: Unable to close any issue even allowed reporters from configuration.

Post by cas »

Based on this information support is rather difficult, it depends on possible configuration changes you may have made.
For eaxample did you change anything in the workflow or is this a clean installation?
Did you install plugins that may impact this?
And so on....

Joachim082
Posts: 2
Joined: Feb 05, 2020 2:21 am

Re: Unable to close any issue even allowed reporters from configuration.

Post by Joachim082 »

I have the same problem - I haven't installed any plugins and the setting allow_reporter_close is set on all projects. I am using version 2.23.0

cas
Posts: 806
Joined: Mar 11, 2006 11:08 am
Contact:

Re: Unable to close any issue even allowed reporters from configuration.

Post by cas »

did you check workflow settings?

Arioch
Posts: 2
Joined: Apr 24, 2020 10:36 am

Re: Unable to close any issue even allowed reporters from configuration.

Post by Arioch »

Let me tell you something strange....

I just installed Mantis for a team of 3.
MS IIS, last PHP (Fast-CGI) , last MariaDB, MantisBT 2.24.0 with ActiveDirectory integration.

The only added plugin was Import/Export to move data from my office desktop where i did proof of concept to the server i was given.

My memory is not veyr sure, i am not PHP guy and this all was a bit of journey into unknown for me and for others too.
So memory of details and exact sequance of events is rather blurred.

So, my LDAP/AD user has Administrator rank.
My another programming peer got Developer rank.

And there was N, from a business-domain sphere, who formulates tasks for us, and she is not very bright with computers.
So i initially just assigned her Author rank, thinking it would be enough for her to manage her own (created by her) tickets.
Later i upranked her to Developer.

Then i started to enter the bugs i was working on (we used MS Word document, ugly i know, but "we here always worked like that" and "who will be maintainer and bear responiosibility?" prevented changes) into Mantis, assigning them to myself, edited them to retroactively set N as reporter, and then fixed them and marked so. I was kind of growing the meat over the skeleton.

Her learning was not instant, for example the first time she commented on an issue she did by EDITING it instead of adding a bugnote/comment.
Still she started uptaking.

Few days later i reprimanded her for learning slow - she was not closing the issues that i marked as fixed and by talks with her i knew she confirmed the fix few days ago. I did not want to press her with any schedule, but still leaving issues open kind of defeats the idea. And bad habits are easy to get, hard to fix.

Then she said she had no option to close the bugs! There were some states available for her to switch to (sorry, do not remember the exact list), but closed was not one of those. I impersonated into her user - and that truly was so.

What was more strange, the bugs that he genuinely reported - she could close.
But the bugs created for me, where i retroactively set her as the reporter - she could not!

I upranked her to Project Lead (and by offline hierarchy she exactly is) then hoping it will give her the "Close" button. It did not.

I had no more time to spend on it, i told myself to investigate it later when i would get any experience with Mantis, and for a while go working on other pressing issues.

Few our later, dead night that dead or maybe morning next day, i found some tickets closed, as they should had been.
I contacted N and she said the "Close" button appeared for her. Including the issues i created as admin to later mark her as the reporter.

There seemed no repeat of the problem.

So in retrospect it looks as either transaction or caching issues.
I may speculate that when IIS shot down all PHP processes, and then N logged back hours later, and IIS launched PHP again, so perhaps some caching was invalidated or maybe a transaction was commited, dunno. And the user grants were resynced and it all started to work.

But the initial experience was that strange. She could not close tickets that she was reassigned ownership with.
And there seemed ot be no explanation to that in Adming Guide nor in the GUI settings.

Post Reply