We're using JIRA 7.1 Software, with a definite incoming Mail.
Is it possible to attach the incoming mail to the issue in .eml?
We developed a plugin for JIRA 4.3 with the SOAP API, but, with the new API, the script can't work.
Here is how it looked like in JIRA 4.3:
Does someone know how to do it with JIRA 7.1?
JIRA 7.1 build in mail handler does not have such function. You will need a plugin for it.
If you dont fancy develop your own plugin, you can always pick a solution from Atlassian Market. There are few plugins that can attach email. One of them is EMH:
When you say the test failed, what happened there exactly?
would be great if you can create a ticket here:
and provide more information.
Hi @Hangsu Ma,
The fail was only my fault
I have another problem right now
I have my Project "Crash Tesr", key "TC". Is it possible to create an issue with a key different of TC-1, TC-2, TC-3... SUP-1 for example?
Moreover, does your Mail Handler always create a new issue when I send an email? Can he recognise an issue key to add a comment?
Best Regards, Damien.
The issue created by mail handler in a project is always using the project key. I am guessing you just need a way to differentiate issues created from mail handler and issues created by user. If that's the case, they you can try set email handler to create a specific type of issue, or add a label on the issue.
For the comments, yes, if your email subject contains a valid issue key, it will be added to that issue as comment. Or if your email is a reply to a email which created an issue through mail handler, then it will always become a comment of that created issue.
Replace the SOAP calls with a REST equivalent - look under issues in https://developer.atlassian.com/jiradev/latest-updates/soap-and-xml-rpc-api-deprecation-notice/jira-soap-to-rest-migration-guide#JIRASOAPtoRESTMigrationGuide-Issues
I tried to use this link to help me changing the plugin. But, it don't really help me, for this, we use different scripts java/shell.
And, a lot of methods used are not present in your link.
As example, is the script 4.3. And what I tried to do in .
The changes between the two scripts are too much important to juste use this guide
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs