1117946 - Ability to set bug_ignored flag via email_in.pl

Status: NEW

(Bugzilla :: Incoming Email, enhancement)

Description

[Albert Ting]

There should be a method to set the bug_ignored flag via email_in.pl, similar to how one can set a field via the '@' syntax.

Comment 1

[cemca news]

In the context of managing bugs or issues through email interactions, it is essential to enhance the functionality of the system by providing a convenient method to set the "bug_ignored" flag. Currently, this can be achieved using the '@' syntax, which allows users to set a particular field. However, extending this capability to include the "bug_ignored" flag will significantly improve the overall user experience and streamline the bug management process.

When users interact with the "email_in.pl" script, they can already leverage the '@' syntax to modify certain fields of a bug or issue. This feature has proven to be valuable for updating fields such as status, priority, or assignee via email correspondence. Expanding this functionality to include the "bug_ignored" flag will empower users to easily mark specific bugs as "ignored" directly from their email clients.

The process of setting the "bug_ignored" flag via email_in.pl can be straightforward and intuitive. Users can simply include a designated keyword or command within the email body to trigger the flag setting. For example, appending something like "##ignore##" or "#ignore" at the end of the email would instruct the system to mark the associated bug as "ignored."

To ensure security and prevent unauthorized modifications, the system could implement authentication mechanisms, such as a unique email token or password, to validate the user's identity before processing any commands that modify bug attributes.

Additionally, to provide users with more flexibility and control, the script could be enhanced to handle multiple commands in a single email. Users might specify several actions, including setting the "bug_ignored" flag, changing the bug status, and updating the assignee all within one message.

To complement this feature, the system should be capable of sending confirmation emails back to the users, indicating that their commands were successfully executed. These confirmation emails would serve as a verification mechanism and a reference for users to keep track of their bug management actions.

Furthermore, clear documentation and user guides should be provided to inform users about the availability and usage of the "@ syntax" for modifying fields, as well as the newly introduced commands for setting the "bug_ignored" flag. This way, users can make the most of the email-based bug management system and efficiently handle their bug tracking and resolution processes .

In conclusion, introducing a method to set the "bug_ignored" flag via email_in.pl, along with the existing functionality of modifying fields through the '@' syntax, will enhance the efficiency and user-friendliness of the bug management system. By empowering users to interact with the system directly from their email clients, it promotes seamless bug tracking and ensures that critical issues do not go unnoticed even during email-based communications.