After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 251124 - Define filters about user-defined keywords in messages that trigger custom actions
Define filters about user-defined keywords in messages that trigger custom ac...
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: general
3.4.x (obsolete)
Other All
: Low enhancement
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
evolution[filters]
: 554853 (view as bug list)
Depends on:
Blocks: 211122
 
 
Reported: 2003-11-18 22:40 UTC by Conor O'Neill
Modified: 2021-05-19 11:33 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Conor O'Neill 2003-11-18 22:40:28 UTC
I've just had an interesting idea for a new feature.

Everyone loves the fact that URLs become hyperlinks in Evolution.  It saves
you the time of opening up a new  browser and copy-and-pasting...it's just
convenient!  Now this was presumably implemented because websites are often
referenced through email, and this is something that would appear quite
frequently and save the user a lot of time.  Well what if it wasn't just
URLs that could be hyperlinked?  What if custom text could be associated
with a custom action?

I'll give you an example of what I mean.  At my company, we work with a few
internal tools to track bugs in our software.  Bugs are referenced with
call numbers (let's call them TPS numbers).  Now every day at work, I get
over 200 emails, 90% of which contain some sort of reference to a TPS
number.  The way things currently stand, I have to either memorize the TPS
number or copy it from the email, open up the bug tracking system, fill in
the number in the search field, and search for it.  This is extremely
inconvenient when you're doing it 20 times per hour.  However, things would
be greatly simplified if I could create a custom filter for my email client
that allowed me to simply click on the TPS number and have the bug tracking
system open up to that TPS report, just as a browser opens to URLs when
they're clicked.

Sample Email:

"Hey have a look at TPS13076 and let me know if you think this patch will
address it. <Attachment>"

In this example, "TPS13076" would be hilighted or underlined or something
to that effect, and clicking on it would open up my bug tracking system to
"TPS13076" just the way http://www.google.com/ opens up my browser to Google.  

This could be achievable by permitting the user to build custom filters
based on scripts (perl, python, bash, mono-basic, etc...).  The above
example is a simple regex match that any admin with a basic knowledge of
perl could hack up in a few seconds.

Every company I've worked for has their own little tracking
mechanism...TPS, DCR, Call#, DR, etc, etc...they're all synonymous with
"issue".  Allowing admins to customize their email clients for the way
their company does business would be a massive boost to productivity.
Comment 1 André Klapper 2005-11-25 00:40:50 UTC
reassigning jpr's old evolution\miscellaneous bugs to harish
Comment 2 André Klapper 2012-02-14 14:26:01 UTC
*** Bug 554853 has been marked as a duplicate of this bug. ***
Comment 3 André Klapper 2012-02-14 14:26:27 UTC
Chen once worked on this, though the link is now a 404:
https://features.opensuse.org/content/ideas/content-aware-evolution-plugin
Comment 4 André Klapper 2021-05-19 11:33:26 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. 
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines
and create a new enhancement request ticket at
  https://gitlab.gnome.org/GNOME/evolution/-/issues/

Thank you for your understanding and your help.