[Hamara-devel] what privileges/functionality has been kept in bugzilla for admins ?

[Vikas Tara]

On 29/04/15 20:23, Amardeep Singh wrote:
> at bottom :-
> On Thursday 30 April 2015 12:30 AM, shirish wrote:
>> at bottom :-
>>
>> On 04/30/2015 12:10 AM, Amardeep Singh wrote:
>>> in line -:
>>>
>>> On Thursday 30 April 2015 12:07 AM, Amardeep Singh wrote:
>>>> Hi Shirish,
>>>>
>>>> I have assigned you permission for " *canconfirm:*Can confirm a bug or
>>>> mark it a duplicate" can you re-check or try again.
>>>>
>>>> What you are suggesting is this permissions should be global rather
>>>> then admin only?
>>>>
>>>> Here <https://www.bugzilla.org/docs/4.4/en/html/useradmin.html> is
>>>> list of permission options available.
>>> Forgot to mention the current permission allowed globally is "editbugs"
>>>
>>> Amardeep
>>>>
>>>> Thanks,
>>>> Amardeep
>>
>> <snipped>
>>
>> something seems to be wrong here. I had asked on the bugzilla-support 
>> mailing list just to confirm the behaviour I had seen with bugzilla 
>> before and this was his reply.
>>
>> Subject: Re: how to disassociate a bug mistakenly put as a duplicate 
>> of another bug ?
>> Date: Wed, 29 Apr 2015 18:34:12 +0100
>> From: Gervase Markham <gerv at mozilla.org>
>> To: shirish <shirish at hamaralinux.org>
>> Newsgroups: Mozilla.support.bugzilla
>> References: 
>> <mailman.2489.1430328221.29279.support-bugzilla at lists.mozilla.org>
>>
>> On 29/04/15 18:24, shirish wrote:
>> > Hi all,
>> > Is there a way to disassociate a bug which was mistakenly put as a
>> > duplicate of another bug ?
>>
>> Yes. Just reopen the bug.
>>
>> Gerv
>>
>> So what should have happened is that bug should have been closed the 
>> moment I made it a duplicate and I should have had the possibility of 
>> re-opening the bug. As shared by you, I am only able to confirm bugs.
>>
>> In almost all open-source projects the bug-reporter does have the 
>> authority to reopen a bug. There are numerous benefits of it, the 
>> easiest is to an update breaks the functionality of the bug which was 
>> resolved. Second is if the bug-reporter is not happy with the admin's 
>> resolution. If we want to have honest feedback from our users then 
>> that 'privilege' or 'right' would need to be shared.
>>
>> What could be done is that you could have a count of say opening 10 
>> bugs or 15 bugs which need to be confirmed by admin or users but that 
>> 'right' or 'privilege' would eventually need to be given. This does 
>> gamify bugzilla little bit but did read some months back that they do 
>> have ideas to gamify bugzilla as it's used by only 'serious people' 
>> or that's what they were claiming.
>>
>> Anyways, look forward to feedback and hopeful change in this regard.
>>
>> The easiest way to see how bugzilla is functioning in other places is 
>> to see bugzilla's implementation on Mozilla. Try doing what I was 
>> trying to do here (even as a new user) and see the difference.
>>
>> Of course it needs to be a valid bug, not so hard if you take the 
>> alpha nightly build from Firefox or Thunderbird and try to use it 
>> through some phases. The moment it breaks, look at the bugzilla db 
>> with the version number, put it up with that build details, make it a 
>> duplicate and then reopen it.
>>
>> Look forward to feedback.
> I am not able to understand Shirish your expectation here.
>
> Are you saying bugzilla doesn't have functionality to re-open bug by 
> user?
> or the behaviour you expecting doesn't exists in bugzilla?
I think Shirish is saying the reporter should be able to reopen a bug - 
but at the moment they can't due to permissions settings on our bugzilla.

I guess the reporter of a bug should be able to reopen it.

Is there a specific permission that covers this scenario?