Apache OpenOffice (AOO) Bugzilla – Issue 117094
Cannot add comment to my own issue any more: No permission to change "ever confirmed" field
Last modified: 2016-04-07 08:37:12 UTC
Created attachment 75925 [details] error displayed in browser I wanted to add information to an issue I filed before the migration to the new infrastructure. It is not possible and gives me the error attached. However, I did not try to change the said field.
Reset QA Contact to new default
I'm having the same problem. I'm also working from a Mac OS X (firefox or safari), if that's relevant. For those who don't want to be bothered with attachments, the warning, displayed in large font with bright red background highlighting, is: " You tried to change the Ever confirmed field from 1 to 0 , but only the assignee of the bug, or a user with the required permissions may change that field. " Of course, I wasn't trying to change anything about the status of the bug, let alone a hidden field. If it's relevant, the bug report I was trying to update was issue 113554.
For the benefit of anyone else who ended up here because they have been getting the same error, I should point out that a work-around is to add a new attachment to the issue and then include your comment from the add-attachment page.
Thanks for the workaround. Is st's comment a fix? If yes, please provide mor details.
I'm also having this problem, trying to add a comment to #112686. Interesting to note, below the comment box on this issue, I see "Status:UNCONFIRMED", where "UNCONFIRMED" is static text (i.e. I would not be able to change it if I wanted to). On Issue #112686, below the comment box the status "UNCONFIRMED" is a drop-down box, with options for "UNCONFIRMED" and "RESOLVED". Although I am not changing that field, I wonder if this has anything to do with the problem. Let's see if I'm allowed to add this comment...
(In reply to comment #5) > I'm also having this problem, trying to add a comment to #112686. > > Interesting to note, below the comment box on this issue, I see > "Status:UNCONFIRMED", where "UNCONFIRMED" is static text (i.e. I would not be > able to change it if I wanted to). On Issue #112686, below the comment box the > status "UNCONFIRMED" is a drop-down box, with options for "UNCONFIRMED" and > "RESOLVED". Although I am not changing that field, I wonder if this has > anything to do with the problem. did you have CANCONFIRM right previously, granted by the OOo QA team? See http://ooo-wiki.apache.org/wiki/Canconfirm_Rights "Common" users can not modify certain fields. In the OOo times, one had to request for CANCONFIRM rights as explained in that wiki page. If you *had* those right granted in the old bug-tracker, you still have them.
I have never requested any additional rights above the defaults, so assume I did not have CANCONFIRM. I am not trying to set the issue to confirmed though - I am just entering text in the "Additional Comments" box and clicking "Save Changes", without changing any other fields. It appears the problem may be related to the fact that I have the option of setting Status to either "unconfirmed" or "resolved". Even though I am not changing that option, by leaving it as "unconfirmed" something in the background seems to be trying to set an "Ever confirmed" field (which I cannot even see).
Same problem here (using Firefox 11b2 under Windows 7 Starter).
getting rid of value "enhancement" for field "severity". For enhancement the field "issue type" shall be used.
Is anyone still seeing this error? Or did it clear up with the update to BZ 4.2.4?
I've just successfully added a comment to Issue #112686, on which I previously encountered this problem. Appears OK to me.
Appears to be working now, per mbourne.