309560 - hook for info about external manipulations desired in results.html.tmpl

Status: RESOLVED WORKSFORME

(Bugzilla :: Extensions, enhancement)

Description

[Anton Ivanov]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

Changing a bug in bugzilla may have side effects if these changes are mirrored
to some external system (in my case, salesforce).
The result template should contain a hook to invoke templates that describe the
results of these external manipulations.  I propose adding the 2 lines marked
with -->
      <h2>[% title.$type %]</h2>
 -->  [%# Show results of external manipulations related to the changed bug %]
 -->  [% Hook.process("external") %]
      [% PROCESS "bug/process/bugmail.html.tmpl" mailing_bugid = id %]


Reproducible: Always

Steps to Reproduce:

Comment 1

[Max Kanat-Alexander]

Agreed, it would be a useful hook. I think that perhaps it should go after the
bugmail template, though.

And we should call it something less specific than "external," something more
about where it happens.

Comment 2

[Anton Ivanov]

I think it belongs between the description of what happened to bugzilla proper
and who got notified about the changes.  But it's a minor point.

I don't have a better idea about a name since I only have my usecase in mind :)
Maybe "additional_info"?  Kinda clumsy.  By "where it happens", do you mean
location on the page?  I'm more used to name that reflect the function rather
than the physical location :)

Comment 3

[Frédéric Buclin]

Only security and dataloss fixes will be accepted on the 2.20 branch. Moreover, 2.22 has been released too, so no more enhancement bugs will be accepted on this branch too.

Comment 4

[Frédéric Buclin]

This bug is retargetted to Bugzilla 3.2 for one of the following reasons:

- it has no assignee (except the default one)
- we don't expect someone to fix it in the next two weeks (i.e. before we freeze the trunk to prepare Bugzilla 3.0 RC1)
- it's not a blocker

If you are working on this bug and you think you will be able to submit a patch in the next two weeks, retarget this bug to 3.0.

If this bug is something you would like to see implemented in 3.0 but you are not a developer or you don't think you will be able to fix this bug yourself in the next two weeks, please *do not* retarget this bug.

If you think this bug should absolutely be fixed before we release 3.0, either ask on IRC or use the "blocking3.0 flag".

Comment 5

[Max Kanat-Alexander]

Bugzilla 3.2 is now frozen. Only enhancements blocking 3.2 or specifically approved for 3.2 may be checked in to the 3.2 branch. If you would like to nominate your enhancement for Bugzilla 3.2, set the "blocking3.2" flag to "?". Then, either the target milestone will be changed back, or the blocking3.2 flag will be granted, if we will accept this enhancement for Bugzilla 3.2.

This particular bug has not been touched in over eight months, and thus is being retargeted to "---" instead of "Bugzilla 4.0". If you believe this is a mistake, feel free to retarget it to Bugzilla 4.0.

Comment 6

[Frédéric Buclin]

This template has a hook before calling bug/process/bugmail.html.tmpl since Bugzilla 4.0 thanks to bug 372979.