Configuring Trackers and Forums to Read from Inboxes
You can use other E-mail accounts to send no-reply emails directly to trackers or forums.
You can configure E-mail Inboxes in the same E-mail Inboxes and Polling page in the System Admin tab by clicking the name of the inbox configuration. You can also add a new inbox configuration by clicking New E-mail Inbox under the E-mail Inboxes tab.
After the inbox is configured, navigate to the configuration page of the target tracker or forum, and assign the inbox to the tracker or the forum.
The tracker then shows the E-mail address, that you can use to submit new tracker items using E-mail.
E-mail sent to tracker e-mail addresses creates new tracker items with the following mapping:
E-mail | Tracker item |
|---|---|
Sender | Submitter |
Priority | Priority |
Subject | Summary |
Body | Description |
AnyE-mail attachment is also attached to the generated tracker item, along with the email itself (e-mail.eml).
You can specify additional tracker item attributes using {attribute : value [, ...] } in the E-mail subject.
Additional attribute may be required, if the target tracker has mandatory attributes.
For example, to send Codebeamer bug reports using E-mail to bugs@codebeamer.com, you must specify at least the version or the release where the bug was detected:
From: You
To: bugs@codebeamer.com
Subject: Sending e-mails to trackers fails ${Detected: 5.7.0; Priority: High; Severity: Critical}
Bug description here
To: bugs@codebeamer.com
Subject: Sending e-mails to trackers fails ${Detected: 5.7.0; Priority: High; Severity: Critical}
Bug description here
You can define multiple attribute values in a single ${ } block, by separating them with a semicolons ;.
You can assign multiple values to an attribute by separating them by using commas ,.
You can include any number of ${ } blocks in the E-mail subject, preferably at the start or end.
You can separate attributes and values by using colon :or equalsign =.
Attributes can be identified by any of the following:
• The Property name for example, priority, severities, assignedTo, startDate, endDate, estimatedHours, choiceList[0]. To view Property names, select the Show property name checkbox on the Fields tab of the tracker configuration page.
• The Label field for example, Priority, Severity, Assigned to, Start Date, End Date, Planned Hours, Detected Version
• The Title field, if any. for example, Detected
• The localized Label field or Title field according to the Language configured in the Codebeamer account of the e-mail sender. For example, for German language: Priorität, Auswirkung, Bearbeiter, Beginn, Ende, Gepl. Aufwand (h), Betroffene Version
• Any abbreviation of the localized Label or Title field, as long as it uniquely identifies an attribute. For example, Prio, Start, End, Planned, Detected is valid, but Assigned is invalid because it is ambiguous :Assigned to or Assigned at.
The format of attribute values depends on the Type of the attribute as shown in the following image:
• Text is plain text, and must not contain commas, semicolons or curly braces. This restriction does not apply to Summary, because the item summary is filled from the e-mail subject.
• Integer and Decimal values are numeric with an optional sign. The Decimal point is, for example, ${Planned Hours: 4.5}.
• Boolean values can be true or false.
• Date values are specified as YYYY-MM-DD [hh:mm], the time-of-day part 24h is optional. You can also use the localized date format configured in the Codebeamer account of the e-mail sender. For example, ${End: 2011-07-30 20:00} or, if the sender has a German account: ${Ende: 30.07.2011 20:00}
• Member values must identify project members and/or(if multiple field values are allowed) project role.
◦ You can identify a user or member by any of the following:
▪ The Codebeamer username. For example, ${Assigned to: support}
▪ The email address of the user defined in the Codebeamer user account. For example, ${Assigned to: support@ptc.com}
◦ You can identify a project role by:
▪ The internal role name, For example, Project Admin, Developer, Stakeholder
▪ The localized role name according to the Language configured in the Codebeamer account of the e-mail sender. For example, for German language: Projektleiter, Entwickler, Beteiligte
• Choice values can have a value from a static Choice list or items from a referenced tracker or category.
◦ Static Choice list values. For example, priority, severities can be identified by:
▪ The choice option Id, for example, ${Priority: 1}, where 1 is highest priority and 5 is lowest priority.
▪ The choice option Name, For example, ${Severity: Blocker}
▪ The localized choice option Name according to the Language configured in the Codebeamer account of the email sender. For example, for German language: ${Priorität: Hoch; Auswirkung: Kritisch}
◦ Dynamic reference values for example, Detected/Target Versioncan be identified by:
▪ The interwiki link of the referenced Codebeamer object. For example, ${Target Version: 5.7-RC}
▪ The object Name, for example, ${Detected: 5.7.0}
As a rule of thumb, specify additional attributes exactly as you see them on the appropriate Codebeamer page.
If you report a New Bug using the Codebeamer GUI as shown in the following image:
 | • You can must specify the Tracker using its e-mail address in the To field. • The reply mail contains a link to the newly created tracker item. In case of a failure, the reply email describes the reason for not creating the tracker item |