Bug 161614
| Summary: | X-Bugzilla-Reason: Flag change | ||
|---|---|---|---|
| Product: | [Community] Bugzilla | Reporter: | Dave Jones <davej> |
| Component: | Bugzilla General | Assignee: | PnT DevOps Devs <hss-ied-bugs> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.2 | CC: | kbaker, nelhawar, pfrields |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-12-02 02:18:54 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Red Hat Bugzilla is now using version 3.2 of the Bugzilla codebase and therefore this bug will need to be re-verified against the new release. With the updated code this bug may no longer be relevant or may have been fixed in the new code. Updating bug version to 3.2. now in the bugzilla email headers there are: X-Bugzilla-Flags: [% flags %] --> that would contain list of all the flags that were changed and the status they were changed to also X-Bugzilla-Reason: [% reasonsheader %] --> would contain a flag change action notification. Noura Noura, is this fix upstream or just a customisation in Red Hat bugzilla? Hi Kevin, the X-Bugzilla-Reason: [% reasonsheader %] part is in upstream bugzilla. but the X-Bugzilla-Flags: [% flags %] --> that was a customization requested by bug #470345 Noura Hi Noura, wouldn't the X-Bugzilla-Flags be useful to the upstream? Any reason why Red Hat should carry this patch? (In reply to comment #5) > Hi Noura, > > wouldn't the X-Bugzilla-Flags be useful to the upstream? Any reason why Red Hat > should carry this patch? I agree. Noura can you file this bug upstream and create a patch against their cvs head that implements the flags header? Thanks Dave okay i have created a bug upstream and attached a patch to their bugzilla to it, basically the upstream patch is different from our patch in one thing which is where we check for flag visibility as upstream bugzilla doesn't have this flag visibility feature yet. Noura |
>Would it be possible to add a X-Bugzilla-Reason: Flag change >to bugzillamail so these state change mails can just be procmailed away ? >The vast majority of bugzillamail I get these days consists of >"PM ACK", and such which creates so much noise, that reading bugzillamail >has basically become next to worthless for me personally.