Tibor Hegyi [META-INF] Atlassian Partner

@Mauricio Ferrer Have a look at the Better PDF Export app and its companion automation app I believe they will meet this requirement.

Email This Issue can also attach the original emails (hence the complete email correspondence) to the issue as eml file attachments. Hence, they are available for Rovo right away.

Hi @Mathew Lederman, If you're interested in having an Email This Issue action in Jira Automation with attachment capabilities, please contact us or me directly to discuss the details. It has been on our roadmap for a while and we're ready to rethink it with you and implement it in a way that it helps you with your…

Hi Nico, can you please contact our support channel via https://metainf.atlassian.net/servicedesk/customer/portal/1 or support@metainf.atlassian.net? To track down these issues, we will need some details, screenshots, potentially logs. Our tech team will be able to assist you to rectify the config or recommend a…

Hi Anton, I recommend you contact our support channel at support@metainf.atlassian.net so that our team can help you figure out what's going wrong. We will propagate the solution back here so that the community may benefit from it. Regards, Tibor

Hi @Joao Zampa though we do not yet support DMARC, our emailing app for Jira supports webhook based alerting when an incoming emails fails to be processed for any reason. If this is a major concern for you, please check out the pages I linked, it may be helpful to you. Regards, Tibor

Hi everyone, we deeply apologize for this trouble, the fix for this issue is being released over the next days. We will provide a description of the solution to fix issue versions in the db. Tibor

I'm with Email This Issue and I can confirm, Dirk's response. With this app, you can set up different auto acknowledge emails. If you need help setting this up, please let us know.

Hi @Amir Ghaemian , Email This Issue has its own mail handlers. The new mail handler type called "Next-gen Mail Handler" allows you to build your handler logic from building blocks. Documentation: https://metainf.atlassian.net/wiki/spaces/PLUG/pages/436469838/Next+Generation+Mail+Handlers…

Well, it will take a while now, but we include the fix in the next version most probably end of September. 

Hi all, We had a screensharing session with Greg and identified the issue. What happened was that if a customer sent an email as a reply to a former notification, the comment was added to the issue as expected. However, the Public Comment Added notification was sent back to the email sender with the comment text. So the…

Hi, Just open the Configuration tab in the add-on administration and find the Permissions section. Here you can set groups or roles to control access to the button. Regards, Tibor

Hi, I'm from META-INF, Vendor of Email This Issue. The biggest difference is that Email This Issue includes a complete email solution while Notification Assistants being a nice product, allows you to send beautiful emails upon events. With Email This Issue however you can send emails manually, upon events, or from workflow…

Hi Stefanie, Please make sure that you have a Mail Handler Context for both Email This Issue Mail Handlers. It is important that Mail Handler Contexts cover your projects and issue types for which you process emails. Regards, Tibor

Hi, Without seeing your mail handler configuration, it is hard to figure out causes but a typical mistake we meet frequently is the following: There are multiple Incoming Mail Handlers using the same IMAP/POP mail box without catch email addresses. Jira mail handlers are capable of commenting any issues in your Jira, not…

Hi Francis, can you please recall what you did to solve this? We experience the same problem. Thank you, Tibor

well, let me explain again: * Administration > Issues > Permission Schemes * Open one of the permisison schemes * Scroll down and find the permission "Schedule Issues" * Make sure it is configured properly for your project * Also make sure the Due Date field is on the screens your project uses: * Administration > Issues >…

Please read the docs to understand it: https://confluence.atlassian.com/jira/managing-project-permissions-185729636.html

Open the project's administration page, go to Permissions and check Schedule Issue. You will see who is assigned to this permission. It may be empty or set to some default project roles your users are not member of.

Hi, Your user will need Schedule Issue permission as well. This drives who can set the Due Date field. Also make sure the Due Date field is on the screen used for creating, editing or viewing the issues. Tibor

Hi Shawn, This is not possible in JIRA out of the box as the default mail handlers cannot populate fields. There are two addons that may help you: Enterprise Mail Handler, it supports both Cloud and Server versions of Service Desk: https://marketplace.atlassian.com/plugins/com.javahollic.jira.jemh-ui/cloud/overview Email…

hi, In the workflow screen, submit buttons are named after the transition. This means that the "Cancel" button (to cancel the issue) receives its name from the corresponding workflow transition. You must rename the transition to "Cancel issue" in order to rename the button. You can rename the transition in JIRA's workflow…

Yes, it is easy. Open the Field Configuration your őprojects use, and configure the renderer for the text custom fields. See docs: https://confluence.atlassian.com/jira/configuring-renderers-185729478.html

Hi Tim, Email This Issue addon can initialize issue fields (including Assignee) based on email content, sender or recipient. See details here: http://www.meta-inf.hu/wiki/display/PLUG/Field+Contexts Regards, Tibor

All i can offer is a screensharing on Monday. Please send me an email to arrange a meeting

well, I have never heard of a similar problem. Are you using Email THis Issue handler with JIRA Service Desk? Because if you use JSD and your portal is open for public signup, JETI creates customer accounts (just like JSD Mail Handler would). But customer accounts do not take JIRA license.

Hi,I suppose the "'Create users" option is enabled in the mail handler in Incoming Mail.OPen this page, find the Mail Handler, click Edit next to it, open the second page in the dialog and check for this option. If ticked, JIRA API creates the users. If unticked, no users will be created.Tibor

Hi Ashely, Please see the tutorials we have in our documentation to setup an Email This Issue Mail Handler: http://www.meta-inf.hu/wiki/display/PLUG/Setting+up+Customized+Notifications http://www.meta-inf.hu/wiki/display/PLUG/Setting+up+an+Email+Help+Desk Also to have a kind of autoreply to the sender, find details…

Hi, though the question is quite old, Email This Issue can easily do this. You can configure automated event notifications that will be sent with the user's email in From. Tibor

Hi Philipp, What you can do now: If you leave Project empty in a Context, then the Context will apply to all projects. Likewise, if you leave type empty, the Context will apply to all types. This means that varying project and type, you can make Contexts cover one or all project(s) and one or all type(s). What we are…