Tibor Hegyi [META-INF] Atlassian Partner

Hi Sharon, JETI does this for you. But it is also available as a core feature in JIRA.

Hi Bruce, This is not possible at the moment. SLA field types have JSON structured values, which cannot be parsed with the current Template API. We are implementing the support for JSD fields. Please watch this issue for progress: https://metainf.atlassian.net/browse/JETI-1415 Tibor

Do you have a post function sending the email? If so, move the post function down in the post function list. Perhaps set it to be the last one. This would make the field values saved before the email is sent.

Hi Ciaran, I'm unsure about open-source plugins, but Email This Issue is a fairly priced addon and can update issues from incoming emails, also it can execute transitions on them. Find details here: http://www.meta-inf.hu/wiki/display/PLUG/Field+Contexts regards, Tibor

Hi Andrew, to send issue details to externals you need to use addons in JIRA Cloud. I know two of them: * JEMH - this is a mail handler, not sure about how you can use it to send emails, but I believe it is capable of doing that * Email This Issue for JIRA Cloud - this is all about sending manual and automated emails from…

Hi, The addon: SD Extensions just offers this. Tibor

ok, I clearly understand what you mean now. Unfortunately it is not possible to change recipients depending on the selected template in the email screen. Tibor

Hi Bruce, Are you looking for ways to configure it in event notifications? E.g. if an issue is updated, send a notification email with template A to recipient A, and another one with template B to the reporter? If this is what you'd like to configure, it is not possible at the moment. We have already implemented this…

Hi Bruce, You can setup up default recipients via the Default Setting feature: https://www.meta-inf.hu/x/mgAXAg It allows you to specify a scope (project, type, JQL) and configure default recipients. When you open the Email Screen, the defaults will be loaded. Tibor

Just noticed, you are on JIRA Cloud! If this is the case JEMH is superior to JETI in the Cloud as JETI's Cloud Mail Handler will be released soon while JEMH is already available. On JIRA Server JETI Mail Handler is already available.

Hi Sagar, I'm from META-INF, vendor of JETI. I suppose you want to read about customers experience here so I'm not going to push JETI over JEMH. I believe both products are suitable for the purposes you mentioned. In case you have any specific questions on JETI, I'm here to answer them. Cheers, Tibor

To determine the manager of a user, we normally recommend the following strategy: * for users having a manager, story the manager's user name (or user key) as a user property in the user profile * if the manager infromation is available in Active Directory / LDAP, synchronize the user property from AD/LDAP so that you can…

Hi David, The problem is that your expressions for reporter and priority contain only one capture group, but the rules are configured with Capture Group 2 and Capture Group 3 respectively. Please change both of them to Capture Group 1. Read more on capture groups and…

Hi David, In JETI, you need to do the following: * Enable Field Initialization in the JETI Mail Handler * Create a Field Context and add field rules to initialize fields for new issues or when a comment is added * A field rule example could look like this (below prepared for the @component tag):* Goal: Initialize field for…

Hi Nancy, how do you want to embed images? As HTML <img> tags? There is not other way. You cannot really embed them but add an <img src="absolute URL to the image" /> tag . This means, you cannot refer to a file in your network but only to an image that is served by a web server. E.g. add this to a template: <img…

Hi, Email This Issue comes with an Email Audit Log. The audit log is either global (see the Emails tab of the config screen) or the Emails issue tab at the bottom of the issue. The audit log contains all incoming and outgoing emails related to issues: http://www.meta-inf.hu/wiki/display/PLUG/Email+Audit+Log Also Email This…

Creating a new listener may not help you, because unless you remove the notification scheme from the project, JIRA will dend event notifications. If you remove, issue updated event grom the scheme, your listener will have to implement the update notification as you described. There may be several addons that support what…

Hi, Watchers will get notifications if: * there is a Notification Scheme configured in the JIRA Project and * the "All Watchers" recipient is configured for events in the Notification Scheme Either of these is not true. Please check your projects and the notification schemes. Tibor

Thank you Jobin.What if the field is a multi user picker? This is the case actually I phrased my question incorrectly.

Is the component field filled in the transition view or stored in the issue prior to clicking Resolved? Case A: component is set before clicking Resolved: Add an additional transition to the workflow, also called Resolved. This will move the issue to Closed. Add a Condition to the transition that checks if Component is set…

Hi Markus, Let me answer your points. Define for each relevant event type a template It not necessary to define different templates for each event types. You can create one template and associate it with the Context. Then if you don't select a template in the Event configuration page, JETI will use the template selected in…

Can you please quote here the velocity snippet you added to the template?Jira restart will reload the template vm files.

Place it in your email template that you create with JETI. See our docs: https://www.meta-inf.hu/display/PLUG/Customize+the+Template+Used+by+Email+Button

Sorry, a closing parenthesis was missing, it is correct in this: #set($formatter = $!jetiFieldFormatter.getJavaDateTimeFormat("dd/MMM/yy")) You can put this anywhere in the template, the best is to put right at the first place you need the formatter.

The related documentation page is here: https://www.meta-inf.hu/display/PLUG/How+to+Format+Date+and+Time+Values One example is: #set($formatter = $!jetiFieldFormatter.getJavaDateTimeFormat("dd/MMM/yy")$!jetiFieldFormatter.formatSafely($formatter, $issue.getCustomFieldValue("customfield_12345"))

Hi Mark, Yes, definitely you can access fields in the linked issues. This documentation page explains how to access linked issues from the issue being sent. https://www.meta-inf.hu/display/PLUG/Add+Issue+Link+Information+to+Your+Template You'll be able to iterate through the linked issues, select those you want and extract…

So, the Systems, etc queues are also based on some JQL filters. E.g. "component = Systems" or "area = Security" etc. All you need is an operation that sets these fields on which the queues are based. Once done, the issue will automatically appear in the queues. You don't have to "drag-n-drop" from one queue to another.…

Hi Rob, Queues are essentially JQL filters. If it is possible to phrase a JQL query to collect what you want to see in the queue Triage, you can create it immediately. e.g. create Triage based on this JQL: "status = New". It will grab all requests in status New to this queue. I suppose the question is not as easy as it I…

Hi, I believe both addons can fulfill the above requirements, maybe one exception is scheduled reminders. Scheduling can be achieved with the free JIRA Automation addon that can fire events / call transitions on issue matching a JQL query. Email This Issue then can be configured to send these reminder emails upon the event…

Hi Aristedes, I'm behind Email This Issue with the team of META-INF the vendor. I'm not replying here to push our addon, rather encourage your to provide some details of your current needs and potential future goals. Understanding this, the following conclusions may be drawn: * Basic JIRA functionality is enough - easy…