Bug 1020834 - [RFE] Explicit marking of automatic changes during change of bug
Summary: [RFE] Explicit marking of automatic changes during change of bug
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Bugzilla
Classification: Community
Component: Creating/Changing Bugs
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-18 11:02 UTC by Petr Holasek
Modified: 2016-10-04 04:09 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-02 22:23:18 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Mozilla Foundation 946565 0 None None None Never
Red Hat Bugzilla 565827 0 low CLOSED RFE: FailedQE value in Verified field + update logic 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 869689 0 low CLOSED Email notifications include incorrect changelog 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1158278 1 None None None 2021-01-20 06:05:38 UTC

Internal Links: 565827 869689 1158278

Description Petr Holasek 2013-10-18 11:02:58 UTC
Description of problem:

Hi,

I think that automatic changes done along to user's bug change should be marked explicitly.

Reproducer:
1. I am in Devel group and moving kernel bug from ON_QA back to ASSIGNED because of some problem described in comments which is not FailedQA.
2. There is automatically added FailedQA into Verified field under my name which breaks accountability a bit.

Expected result:
Mark change Verified: FailedQA as "auto" or something like that.

Comment 1 Jason McDonald 2013-10-21 04:34:54 UTC
The automatic addition of "FailedQA" to the Verified field was added to Bugzilla in Bug 565827. I presume that this was done to satisfy the requirements of the CDW process used for RHEL releases.

The relevant code fragment (from extensions/RedHat/Extension.pm) is:

    881     # REDHAT EXTENSION START 565827 826305
    882     if ($changes->{'bug_status'}
    883         and (grep($_ eq $old_bug->status->name, ('ON_QA', 'VERIFIED', 'RELEASE_PENDING')))
    884         and $bug->status->name eq 'ASSIGNED'
    885         and $user->can_set_partner('FailedQA')
    886         and not grep($_ eq 'FailedQA', @{$bug->cf_verified})
    887     ){
    888         $dbh->do("INSERT INTO bug_cf_verified (bug_id, value) VALUES (?, ?)",
    889                  undef, $bug->id, 'FailedQA');
    890         # Log the change
    891         LogActivityEntry(
    892             $bug->id,
    893             'cf_verified',
    894             '',
    895             'FailedQA',
    896             $user->id,
    897             $timestamp
    898         );
    899     }
    900     # REDHAT EXTENSION END 565827 826305

There are a number of other automatic field changes in nearby code that are also logged to the activity history under the identity of the user making the changes that trigger the automatic change.

While I have no philosophical objection to changing that behaviour, the mandate for Bugzilla's implementation of the CDW doesn't belong to me.  That role is currently filled by Suzanne Yeghiayan (now CC'd on this bug) and you will need to negotiate any change to CDW-related behaviour of Bugzilla with her.

Comment 2 Petr Holasek 2013-10-21 08:48:58 UTC
Jason, thank you for the informations!

Suzanne, what do you think about this proposed change? It seems to me that it won't break anything, just add more verbosity into state changes descriptions.

Comment 3 Suzanne Logcher 2013-10-21 15:38:47 UTC
AFAIK, the QE Department requested this change.  It was not a change requested by Program Management for CDW.  I suggest you start by asking Ben Levenson about it.

Comment 4 Jason McDonald 2013-10-22 02:05:43 UTC
Ben, are you able to comment on the above?

Comment 5 Simon Green 2013-12-03 05:32:46 UTC
This bug is specifically about the CDW. It's about changes made by bugzilla (most of which are defined in extension/RedHat/Extension.pm being attributed in the e-mails to the person making the original change, not the bugzilla user.

Having said that, this is one of those bugs that once you've spent time looking into it, you can fix it straight away. Targeting for sprint13, need to work on a patch for upstream though.

If there are changes required in regards to the CDW, that is a separate bug, and should be filed as such.

E-mails with multi user changes will now look like:

Red Hat Bugzilla <bugzilla> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Group|                            |devel, qa

Simon Green <sgreen> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sgreen

Comment 6 Simon Green 2013-12-05 04:30:36 UTC
Submitted upstream patch for this. It doesn't go cleanly into our code, so I'll do another patch for us towards the end of the sprint.

Comment 7 Simon Green 2014-01-02 22:22:23 UTC
We'll inherit this as part of the upstream merge process. There will be a conflict, but that can be fixed on commit.

  -- simon


Note You need to log in before you can comment on or make changes to this bug.