Forums
Home Product Q&A Discussion groups Articles Ask a question Search
Learning
Events
Champions

Forums

Articles
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Product Q&A
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Create an issue from e-mail and description field got detailed HTML coding

SherryX
SherryX
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
January 16, 2012

We currently have a project using JEMH plugin to create issues from e-mail, all works fine.

Now I need to create a new project to create issues from e-mail as well. So I setup new mail server and service, use the same emh.properties as current project and make up an e-mail from some of the custom fields in the current projects. I did then received the created issue notification from Jira, but the description field has html detailed coding in it, also the custom fields are not save to the database?

Answer
Watch
Like Be the first to like this
986 views

4 answers

1 accepted

0 votes
Answer accepted
Andy Brook [Plugin People]
Andy Brook [Plugin People]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
January 16, 2012

Your email _must_ currently be either (a) "text/plain" content email or (b) be mime multipart with a "text/plain" alternative content payload.

Parsing HTML only emails is not yet supported, please watch https://studio.plugins.atlassian.com/browse/JEMH-367

View More Comments
SherryX
SherryX
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
January 17, 2012

Thanks, it works. By the way, when create issue from the e-mail, I want to change the description to include the message, e.g. "this is created from DEV", do you know how to do that?

Like
SherryX
SherryX
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
January 17, 2012

Andy, I enabled indicateSourcedByEmailHeader=true in emh.properties file but why I could not get the following in the description of the created issue.

[Created via e-mail from: "jiradatafeed.support@test.com.au" jiradatafeed.support@test.com.au]

Thanks for your help

Like
Andy Brook [Plugin People]
Andy Brook [Plugin People]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
January 17, 2012

That flag adds the banner you show. Not sure what 'DEV' is, can you expand?

You can also indicate the Field Processor used to deliver the message: #indicateWhichProcessorProcessedMail=true

Like
SherryX
SherryX
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
January 17, 2012

Thanks, Andy. I was expecting to see the banner but I could not see it. I use the same emh.properties from the existing project and the issues created in that project did have the above banner, so I wonder why I did not get one.

DEV is for development evironment, I was wondering if I can add some helpful information to the description/comment field before it is saved to the issue.

e.g. if I have the following e-mail sent to our existing project:

@field1=value1
@field2=value2
@project=project1

***this is created via web application***More details

I got the following in the created issue (description field)

[Created via e-mail from: "jiradatafeed.support@test.com.au" jiradatafeed.support@test.com.au]

 .this is created via web application***More details

But if I use the above e-mail in my new project:

@field3=value3
@field4=value4
@project=project2

***this is created via web application***More details

I got the following without the banner:

***this is created via web application***More details

I also noticed that the content is a bit different, my new project just copy what ever is on the email include the first three characters "***", but the existing project seems removed the first three characters "***" and add something else, I don't know how to do it. The existing project was setup by other people who already left the company, I have no idea why the two projects got different responds as they have the same emh.properties file?

Like
Reply
1 vote
DeepakBhatia
DeepakBhatia
Contributor
January 16, 2012

Hi,

Please set content type to "text/text" of the email.

Regards

Deepak Bhatia

View More Comments
Andy Brook [Plugin People]
Andy Brook [Plugin People]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
January 16, 2012

a nice idea but this won't help, you'll just get lots of XHTML in the issue, which is surely not the intent.

Like
DeepakBhatia
DeepakBhatia
Contributor
January 16, 2012

Hi Andy, But in my case, it worked as I am sending email from the web site written by us. When I selected the content of the email as 'text/text', it worked.

Like
Andy Brook [Plugin People]
Andy Brook [Plugin People]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
January 17, 2012

Sure, so long as the _content_ is just plain text, that would work, in the example above, not so much :)

Like
Reply
0 votes
SherryX
SherryX
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
January 16, 2012

I expected to have descrption field, e.g.

[Created via e-mail from: "jiradatafeed.support@test.com.au" <jiradatafeed.support@test.com.au>]

Created via the Datafeed Support web page ***
Details (from e-mail)

instead I got the following in the descrition field:

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-AU link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:black'>@reporter=ttswjx<o:p></o:p></span></p><p class=MsoNormal><span style='color:black'>@project=TEST1<o:p></o:p></span></p><p class=MsoNormal><span

Reply
0 votes
SherryX
SherryX
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
January 16, 2012

I added defaultCF default values to emh.properties file and the values appeared correctly in the created issue.

But why it didn't pickup the values from the e-mail? e.g. @test case=case1 (where test case is the custom field name).

Anyone can give me some idea?

Reply

Suggest an answer

Log in or Sign up to answer
Product apps
Apps & Integrations
TAGS
AUG Leaders

Atlassian Community Events

    See all events
    Community
    Forums
    FAQs Forums guidelines
    Learning
    About learning Resources
    Events
    Champions
    Copyright © 2025 Atlassian
    Privacy Policy Terms Security
    Welcome illustration

    Welcome to the new Atlassian Community

    Online forums and learning are now in one easy-to-use experience.

    By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.