119734 - Named changes (canned/stock responses or "comment templates")

Status: NEW

(Bugzilla :: Extension Ideas, enhancement, P4)

Description

[Matthew Tuck [:CodeMachine]]

It would be really cool if we could give a name to a set of changes commonly
made to bugs.

For example, "Kill-Test-Bug" might change resolution to INVALID and add a
comment about not putting test bugs on bmo.  "To-Nobody" might reassign to
[e-mail] and set milestone to '---'.

These would be quick and could be used to prevent people forgetting parts of a
change.

Comment 1

[Matthew Tuck [:CodeMachine]]

*** Bug 137712 has been marked as a duplicate of this bug. ***

Comment 2

[Matthew Tuck [:CodeMachine]]

OK, the comments should allow some sort of variable substitition on reporter,
assignee, qa, etc, so I could say:

$reporter, please ...

Also we would probably want to define group and system changes as well as
individual ones.

Comment 3

[John Levon]

This would make formulaic responses to bad bug reports a thousand
times easier.

Comment 4

[Bill Barry]

I have an idea how this could be done:

1: Create a page called "Create Bug Macro" with a form similar to the multi-bug-change form with a textbox so you could name a set of changes.
2: Link to this page from user preferences so it works just like Saved Searches
3: Add a radio button just above the Commit button labeled "Saved Bug Macro" with a dropdown containing the user's saved macros (only create this if the user actually has said macros)

Comment 6

[Dave Miller [:justdave]]

Bug 223074 has some additional ideas (and some code) for implementing this, including trying to pick possible templates for you based on regexp scores of the initial summary and description?  More ideas to throw in the pot.

Comment 7

[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 "?", and 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.

Comment 9

[Werner Moser]

Are there any chances that this feature will be implemented (in the near future)?

I think, that template texts would be very useful like this: you can create template texts and then connect them to single components or products. When a new bug is created, the configured template is displayed in the comment box.

Comment 10

[Frédéric Buclin]

We are going to branch for Bugzilla 4.4 next week and this bug is either too invasive to be accepted for 4.4 at this point or shows no recent activity. The target milestone is reset and will be set again *only* when a patch is attached and approved.

I ask the assignee to reassign the bug to the default assignee if you don't plan to work on this bug in the near future, to make it clearer which bugs should be fixed by someone else.