Is there a way to use variables in JQL?

[Rob Horan]

I would like to create a set of queries for a dashboard that I can re-use from version to version such that I can use a variable in the JQL.  This would allow me to make a single change which would affect all the filters used on that dashboard.  The only other option is to manually edit every bloody filter.

[Andy Brook · Accepted solution]

Hi Damien,

> Will JEMH delete the email after trying to process it ?

To be specific, JEMH cannot do this.  What JEMH can and will do is indicate that it is has processed/consumed the given message, this indicator is handled by JIRA and returned to the mailserver as 'READ', which is interpreted by the MailServer in specific ways (e.g. it may be marked read or actually removed)

If Messages were not marked 'READ' they would be there the next time messages were polled for, resulting in repeat processing (and NO no message processing)

> Will JEMH leave the email in the mailbox ?

JEMH will leave messages in the mailbox 'UNREAD' if the message is not found to be an expected recipient.  JEMH expects every inbound message found to be addressed 'to' JEMH.  This is confirmed through the catchEmail CSV field and jemhAddresseeRegexps CSV field.  In the simple case of one profile, if the message 'matches' the expected catchEmail/jemhAddresseeRegexp then the message is a candidate for processing, and regardless of outcome, will be 'READ'.

When issues fail to create issues/updates, the sender MAY be notified through the HintOgram feature, usually not. If an unexpected or 'procedural' problem results (eg no project can be found) then where issue creation fails, the message will be forwarded to the Notifications > Forward user.  In any/all circumstances of non-processing, it is always desirable to push the mail on to a Forward user for review rather than block the mail queue, where messages could still remain that can be processed.

> When Email with Directives which are not in White list ?

They are ignored

> Email without subject ? 

For this case, JEMH has a default summary which is used in place, see Profile > Issue : Summary

[AJ]

Hi Andy, 

Thank you for your help.

Damien