{5} Assigned, Active Tickets by Owner (Full Description) (19 matches)

List tickets assigned, group by ticket owner. This report demonstrates the use of full-row display.

bas (19 matches)

Ticket Summary Component Milestone Type Created
Description
#321 How to avoid duplicate tickets? email2trac defect 07/02/13

How to avoid duplicate tickets?! I'm using GLPI (HelpDesk). GLPI triggers emails to an account. I'm using Fetchmail.

The problem is when the GLPI some status updates and then sends an e-mail alert. This turns out creating a new ticket in Trac.

My email2trac.conf

[DEFAULT]
project: /var/trac/projects/claudino
ticket_permission_system: update_restricted_to_participants
debug: 1
black_list: MAILER-DAEMON@
drop_spam : 1
drop_alternative_html_version: 1
email_quote: >
html2text_cmd:
ignore_trac_user_settings: 0
inline_properties: 1
reply_all : 0
spam_level: 5
strip_quotes: 1
strip_signature: 0
ticket_update: 1
umask: 022
verbatim_format: 1
log_type: file
log_file: /tmp/email2trac.log
mta_user: nobody
DEFAULT_keywords  : ServiceDesk
DEFAULT_component : TRAC
DEFAULT_priority  : Alta
DEFAULT_severity  : Normal
DEFAULT_type      : Triagem

[claudino]
project: /var/trac/projects/claudino
cla_keywords  : ServiceDesk
cla_component : TRAC
cla_priority  : Alta
cla_severity  : Normal
cla_type      : Triagem

#328 Better handling of invalid inline properties email2trac defect 08/24/13

We have a few cases where the text in the body of the message matches an inline property request and email2trac exits with a non-zero exit status and the MTA bounces the email with the most unhelpful message:

<trac@trac>: Command died with status 1:
"/usr/bin/run_email2trac". Command output: saving email to
/tmp/tmpa6SfOO.email2trac writing body to /tmp/tmpbJnIAS.email2trac

If you look in the logs, you can see the python traceback from the unhandled exception:

Emailtrac: ProgrammingError:
column "dev02" of relation "ticket" does not exist
LINE 1: UPDATE ticket SET dev02='~$' WHERE id=2161

This was generated by the line:

@dev02:~$ time curl -s -

which was meant to explain the shell command being run but inadvertently attempts to set the (non-existent) dev property to '~$'.

I can think of a few ways to handle this:

1) restrict where the properties setting syntax is valid. E.G.

a few ticketing systems allow the property setting only in first set of lines of the email. As soon as a blank line is encountered, scanning for property setting is turned off. The inline_properties setting could take the values: "on", "off", "top" .... Where top means only the first blank space separated paragraph would have property parsing enabled.

2) return a better error message from the interface. IIRC

anything emitted by the delivery program to stdout will be returned in the bounce message. So catching the error and generating output like:

      line #13 of your message:

         @dev:~$ ....
      attempted to set the property dev and failed. If you
      didn't mean to set a property indent the
      line or use a character other than @ to start the line.

from email2trac (assuming an indented line can not set a property) would be most helpful.


#332 email2trac without updating updater email2trac defect 11/22/13

I want to use trac as a backend support system with an email front-end via email2trac. The problem is that trac defaults to sending out emails for every change to a ticket, so when someone emails a new ticket or a response (via email2trac) Trac emails them the ticket change that they just made (or sends no notification depending on trac config). I want to suppress that so the only notifications they get are changed done by other people.

One solution to this is the trac plugin to change notification behavior: NeverNotifyUpdater . My problem is I can't get email2trac to use this plugin.

Looking at the code for email2trac, is seems to load the trac environment and load my plugins (including NeverNotifyUpdaterPlugin) but I think email2trac is sending notifications from a method that NeverNotifyUpdaterPlugin doesn't see (or hijack for its own purposes).

Maybe there is a better way to get Trac / email2trac not to send out notifications to the updater (AnnouncerPlugin although I don't see how to configure it to do that)?

I'm using 2.7.6 for email2trac and trac 1.0.1.

Thanks,


#445 Trac 1.4 not supported by email2trac email2trac defect 09/21/19
Dear author of email2trac!

Trac 1.4 has been released now.

It looks like that this version is not compatible with the latest
email2trac version. Emails disappear from the mailbox while no tickets
are created.

Debug output from /var/log/syslog:

{{{
Sep 21 16:04:31 selene fetchmail[285]: 1 message for
trac-ticket@webtek.at at luna.webtek.at (1064 octets).
Sep 21 16:04:32 selene email2trac trac: Found trac version: 1.4
Sep 21 16:04:32 selene email2trac trac: TRAC version 1.4 is not supported
Sep 21 16:04:32 selene fetchmail[285]: reading message
trac-ticket@webtek.at@luna.webtek.at:1 of 1 (1064 octets) flushed
}}}

It would be great if this issue could be fixed.

Thank you and good bye,

Thomas

#194 Better way of stripping outlook-style top-post replies email2trac strip signature/quotes enhancement 04/09/10

Note that this works well only in conjunction with "strip quotes only on ticket update" functionality suggested in #192. The trouble with Outlook-style replies is that message forwards have the exact same format as message replies. If you apply this patch without stripping quotes on ticket updates, you will potentially lose important data if someone forwards you an email to start a new request or cc's you in the middle of an existing thread.


#297 Add support for ticket-specific email addresses via wildcards email2trac enhancement 05/19/12

Currently, there is one e-mail address and bug # (and other information) is parsed from the subject field. It would be nice also to support the configuration of wildcard e-mail addresses, one address per issue, like bug243-trac@domain or 243@bugs.domain and such (configured via format string, and via wildcards in the MTA config). (The subject field would be perhaps added on the top of the comment, or discarded)

It would be easier to cc bug mails (to someone not on trac, and to trac itself), without requiring some particular subject text, and the conversation could seamlessly happen over e-mail and web combined.

Notification about ticket changes could be sent with the sender's address Diplayed User Name <234@bugs.domain> (this is what launchpad does), or with the reply-to field modified accordingly.


#307 Bold and Italics to use trac WikiFormatting email2trac enhancement 11/17/12

Currently email2trac translates formatting like this:

  • /words in italics /: /words in italics /
  • *words in bold *: *words in bold *

Is there a way to make these use trac WikiFormatting:

  • ''words in italics '': words in italics
  • '''words in bold ''': words in bold

#331 Update to work with Apache Bloodhound email2trac enhancement 11/12/13

Hi Bas,

Glad to see you noticed the associated thread on the bloodhound dev mailing list.

A bit ago bloodhound made some changes that I believe breaks the previous compatibility with email2trac. I have created a patch that gives some hints for how support for bloodhound might be provided with some limited detection of a bloodhound environment to provide some safety. At the moment I think I have only included the ability to specify a bloodhound product on the command line.


#339 Patch Integration GLPI with Email2Trac. email2trac enhancement 04/01/14

Hello,

I made a simple change to integrate the Email2Trac with tool [1] GLPI. The integration is performed using the subject line of emails sent by GLPI.

The emails that are sent by "GLPI" in the subject have the text "Service Desk #ZZZ" where "ZZZ" is a unique number created in GLPI.

Attached the patch.

[1] http://www.glpi-project.org/spip.php?lang=en


#344 Allow use of inline-properties to identify the source of a ticket comment email2trac enhancement 10/08/14

Unfortunately, users sometimes email issues directly to developers.

The developers can forward these to requests to Trac, and use the @reporter in-line property to make sure that the issue is properly attributed to the original reporter.

Equally unfortunately, users sometimes send emails about existing issues directly to developers without Cc'ing Trac.

Again, the developers can forward these emails to Trac, but there appears to be no in-line property that we can use to tell email2trac that the comment should be attributed to the original commenter.

AFAICT, in-line properties only work for ticket properties, and not for comments, as is documented.

Developers are unable to change the 'From' property in their email clients, for security reasons.


#446 How to fix: email2trac test: ImportError: cannot import name TicketNotifyEmail email2trac enhancement 02/19/20

Hello Bas!

Several years ago we're talking via email about email2trac plugin. I hope you're continue developing and supporting email2trac plugin. As you already uderstanding - I have some a little (?) problem again, but now with email2trac version 2.12.2 (src from git repository) and trac version 1.4 (stable). Our company ask me upgrade as old trac v.0.12.3 to latest stable... I was done moved all as trac to 1.4 and enabled mostly popular plugins for 1.4. Adding email2trac should be a last step, but... but... but...

The message from email2trac in log like:

2020-02-19 19:51:32,322 email2trac test: Found trac version: 1.4
2020-02-19 19:51:32,322 email2trac test: TRAC version 1.4 is not supported

that was not a problem - I finded ticket in yours trac about it and maked changes - add ,'1.4' into code "if version in ....

But after that I geted more seriosly problem for me:

2020-02-19 20:14:16,010 email2trac test:   File "/usr/bin/email2trac", line 2913, in <module>
    from trac.ticket.notification import TicketNotifyEmail
2020-02-19 20:14:16,010 email2trac test: ImportError: cannot import name TicketNotifyEmail

As you remember - I not a profi in python code , can read code and apply the fixes. As I guess the problem near module names in 1.4 trac.

Can you help me with that?

I hope you're not a strong busy atm. I'm ready to testing any idea fro solution problem.

PS: o'course I can made the ticket in yours trac if it need - required?


#380 reply creates new ticket email2trac setup 02/26/16

we changed our notification subject line to:

ticket_subject_template = #$ticket.id @$ticket.owner | $ticket.status | $summary

... and suddenly replies to ticket-notifications do not create comments any more but new tickets.

Versions: (installed from Debian 7 packages)

  • trac 0.12.5
  • email2trac is 2.4.7

/etc/email2trac.conf :

[DEFAULT]
project: /srv/www/trac/env/kunden-trac/
debug: 1
umask: 022
spam_level: 5
reply_all : 0
umask: 022
email_header: 0
alternate_notify_template :
alternate_notify_template_update :
drop_spam : 0
strip_signature: 0
email_quote: >
strip_quotes: 1
ignore_trac_user_settings: 0
black_list: MAILER-DAEMON@
drop_alternative_html_version: 1

[support]
mailto_link: 1
html2text_cmd: /usr/bin/html2text -nobs
inline_properties: 0
ticket_update: 1
ticket_update_by_subject_lookback : 90
email_header: 0
strip_signature: 1
strip_quotes: 0
verbatim_format: 1
always_notify_reporter: 0
no_reporter: 0
no_reporter_email: 1
default_component : 1 support
default_owner: blank-support
default_intern_extern: extern

I also tried setting "ticket_update_by_subject : 1" but it did not help.

What can we do?


#418 Email doesn't create tickets email2trac setup 08/03/17
Hi,

I'm having a problem with the 'email2trac' software.  I expect it's a
problem with my configuration, but I have no idea where.  I've gone
through the docs and tickets and made the changes that I thought would
help, making some progress (thanks to ticket 279), but I'm now at a
standstill (nothing in the audit.log file).

I'm currently running V2.11 of email2trac on a free Amazon EC2 instance
running Amazon Linux.


Installation procedure (run as ROOT):
# Install email2trac
mkdir work
cd work
wget ftp://ftp.surfsara.nl/pub/outgoing/email2trac.tar.gz
tar xzf email2trac.tar.gz
cd email2trac-*
./configure --with-mta_user=editors --with-trac_user=apache
make
make install
cd ../..
rm -rf work


Invocation:
Because the incoming email is generated from a forum as PMs, the "From"
on the incoming message is meaningless, and I need to extract the
originator from the content of the message.  To do this, I use a
.forward file to send the message to a script to filter/modify incoming
messages.  That script creates a "valid" (I hope) message and sends it
to the email2trac script, as follows:
/usr/local/bin/run_email2trac -d -v < ${TMP}/message.out 2>&1 >
/tmp/email2trac.log

A sample of the message.out file is:
 From: testuser
Date: Thu, 03 Aug 2017 03:10:32 +0000
Message-Id: <4u1zhunt3szu.1VytYN2dZNyn-FOlnrAlkw2@tracking.mydomain.com>
Subject: New ticket

  ID test #6

Are there additional header lines that I need to include?

The /tmp/email2trac.log file always ends up empty, and there's no
information in the SYSLOG file.

How can I get more information out of email2trac, so that I can resolve
this?

Thank you.

Peter Ashford

#318 honoration of Reply-to: field in email email2trac enhancement 05/23/13

I would like to have the ability that email2trac honors the Reply-to: field of an email. If the reply-to field is filled in the email, it should be used instead of the From: field

I think this option should be configurable to enable or disable this in your environment.


#367 attachment as raw-attachment? email2trac enhancement 05/28/15

Hi Guys,

first of all: great software, thanks! One nuisance is that attachments are added to the ticket as a link [attachment:file]. When I click on the link, I get a preview window. Unfortunately, trac can't preview most formats, so it's a useless intermediate step. Could you replace attachment with raw-attachment, so the preview is skipped and the original file is downloaded immediately? Or, even better, only to use attachment for formats that trac can preview?

Cheers, John


#376 Not a problem just something that might help others email2trac enhancement 12/08/15

After solving some email server issues because of vlans and firewalls on campus, I finally got my emails to deliver to Trac and the maillog showed the command was being processed but tickets did not post. so I added some redirection output to my command and found that trac.ini was not readable and trac.log was not writeable. So I change permissions on those and it is working now, thanks. I am using Postfix and the command I used is:

"| /usr/local/bin/email2trac -d -v --project=eresources >>/usr/local/log/email2trac.errors 2>&1"

You may want to pass this along with the documentation.

Thanks for the work you have done. Thomas Bennett


#378 Mitigating autorespond loops by implementing RFC 3834 email2trac enhancement 02/20/16

My email2trac and trac are configured to notify the reporter for ticket creation and updates. Occasionally an automated system sends an email, causing it to receive an automated reply, causing it to send its own automated reply, essentially creating a loop. Stopping this requires manual intervention by adding the offending address to notify_reporter_black_list

This could be partly reduced by following some of the RFC 3834 recommendations. Specifically not sending an autorespond in case the Auto-Submitted header is present (unless it is set to no) or the Precedence header is present and set to list, junk or bulk. Trac already sets these headers on outgoing mails.

This however will not stop mail loops with remote mailers that both do not set nor check these headers.


#414 Last Milestone version email2trac enhancement 04/28/17

We are creating ticket from email forarded to trac and by using EmailToTrac?.

We use variables to initialize fields and are trying to intialize the Milestone.

Is there a way to initialize this field (milestone) with the LAST OPEN VALUE ?


#402 Register for https://oss.trac.surfsara.nl/email2trac/ email2trac task 11/10/16
Hi
I'd like to register with this email account if possible, so that I can
contribute to the email2trac project.

thanks

Jacob

--
Jacob Share
Job Search Expert & Professional Blogging Consultant
https://jobmob.co.il/

Follow me on Twitter:
https://twitter.com/jacobshare

Note: See TracReports for help on using and creating reports.