Bug 272388

You need to be logged in and the reporter of the bug, then you can change the severity using the combobox. Click "Commit" after changing the field.

You can also just add a comment, and the bug triaging team will take care of it.

Assuming that "severity" refers to Importance, I'm afraid this was erroneously marked as resolved. I cannot change the Importance of - for example - https://bugs.kde.org/show_bug.cgi?id=413343

As for adding comments, I believe I commented on a few tickets which needed changes in recent months, and I don't remember any being taken caren of.

Members with bugedit rights can edit the severity. This includes all triagers.

There was no need to reopen this.

(In reply to David Edmundson from comment #3)
> Members with bugedit rights can edit the severity. This includes all
> triagers.

In that case, this is broken. I cannot edit this very ticket's "severity".

Why was this ticket marked as resolved?

Arguably, this ticket's "severity" should be wishlist. But of course, it can't be changed :-)

>In that case, this is broken. I cannot edit this very ticket's "severity".

Really? 
Can you go to https://bugs.kde.org/userprefs.cgi?tab=permissions

and confirm if you have editbugs?

(In reply to David Edmundson from comment #6)
> >In that case, this is broken. I cannot edit this very ticket's "severity".
> 
> Really? 

Really


> Can you go to https://bugs.kde.org/userprefs.cgi?tab=permissions
> 
> and confirm if you have editbugs?

Yes

Can I have a screenshot of this severity box and the permissions page above.

Can I have an answer to my question.
Otherwise I don't see why we'd bother providing screenshots for a problem which was supposedly resolved.

I haven't followed what your question was.

People with the editbugs group privilege should be able to edit bugs.
People without should not (the original post was saying they should. Hence closed).

If you have the editbugs groups privilege granted and can't edit bugs, that's a separate relevant bug, but somehow we're talking it here. I wanted the screenshots as it's the fastest way to confirm we're talking about the same things.

(In reply to David Edmundson from comment #10)
> I haven't followed what your question was.

My question is the last sentence of comment #4.


> People with the editbugs group privilege should be able to edit bugs.
> People without should not (the original post was saying they should. Hence
> closed).

The definition of editbugs is "Can edit all aspects of any bug."
The Description does not say people without editbugs should be able to edit all aspects of a ticket, it merely implies the obvious - that reporters should be able to edit the Importance, which they set themselves. In fact, the Description does not say anything about editbugs.


> If you have the editbugs groups privilege granted and can't edit bugs,
> that's a separate relevant bug, but somehow we're talking it here. I wanted
> the screenshots as it's the fastest way to confirm we're talking about the
> same things.

I would argue that would be an additional issue. I think it suffices to state that a new ticket can be filed to track that problem.

(In reply to David Edmundson from comment #3)
> Members with bugedit rights can edit the severity. This includes all
> triagers.

The group editbugs is more restricted. Members in "contributors" group can edit severity:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging#Bug_editing_permissions

"You are restricted to only a few abilities, such as bulk editing, changing the Priority and Severity fields (Importance), or re-opening CLOSED bugs. After getting comfortable with the KDE Bugzilla process, you can request "contributor" privileges from Sysadmin, which will allow you to perform those actions."

Thank you Buovjaga,
If I understand correctly, there are 2 issues (in addition to the one tracked here):
1. https://bugs.kde.org/userprefs.cgi?tab=permissions claims editbugs grants more permissions than it does (like editing Importance).
2. https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging#Bug_editing_permissions says the opposite of what it intends to say (following https://community.kde.org/index.php?title=Guidelines_and_HOWTOs/Bug_triaging&diff=82599&oldid=81937 )

(In reply to Filipus Klutiero from comment #13)
> Thank you Buovjaga,
> If I understand correctly, there are 2 issues (in addition to the one
> tracked here):
> 1. https://bugs.kde.org/userprefs.cgi?tab=permissions claims editbugs grants
> more permissions than it does (like editing Importance).
> 2.
> https://community.kde.org/Guidelines_and_HOWTOs/
> Bug_triaging#Bug_editing_permissions says the opposite of what it intends to
> say (following
> https://community.kde.org/index.php?title=Guidelines_and_HOWTOs/
> Bug_triaging&diff=82599&oldid=81937 )

Indeed, David and me apparently went editing the article at the same time just now. I fixed the headings instead.

The one being tracked here is now resolved. I gave the wrong group name. You aren't in "contributors", hence you don't have the powers. So there isn't a bug \o/

>2. https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging#Bug_editing_permissions says the opposite of what it intends to say 

Fixed.

(In reply to David Edmundson from comment #15)
> The one being tracked here is now resolved. I gave the wrong group name. You
> aren't in "contributors", hence you don't have the powers. So there isn't a
> bug \o/

According to your 2019-11-04 change, this ticket is not a bug report, but rather a mere request for enhancement, so while there is no bug indeed, the issue reported remains.


> >2. https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging#Bug_editing_permissions says the opposite of what it intends to say 
> 
> Fixed.

Thanks

It is a request for a change that has been considered and declined.

(In reply to David Edmundson from comment #17)
> It is a request for a change that has been considered and declined.

None of that resolves the problem.

Also note that the current resolution "NOT A BUG" is incompatible with the current Severity "wishlist".