Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

These Directives must be specifically enabled (e.g. Profile > Directives > Directive Processing Behaviour : Create/Comment).  

...

Translating directives

Where keys and values do not match Jira custom fields or appropriate values, JEMH Aliases allow a) complete key+value conversion into different key+values, b) key replacement, bc) value replacement, this feature allows translation of external values into 'internal' values suitable for use.

...

Directives require no specific Jira permission, but the user under which an activity is performed needs have appropriate permissions. Fo For example, adding email CC header participants as watchers of that issue will require “Manage watchers” permission.

It is possible to limit what users can do with Directives by setting a whitelist, perhaps just with 'priority' or even specific Alias keys that have been defined.  Directives can be limited by whitelist Allowlist or blacklistBlocklist, using both is a little nonsensical, but will mean within the set of whitelisted Allowlisted directives. Those that are blacklisted Blocklisted are then discounted.  

...

Directive Groups

Directive Groups are used to define the User groups that the sender must be part of. If they do not have one of the groups defined then the matched directives will not be processed.

...

Parsing and outcome for content

...

Here is an example of the AtFormat showing common sources of this problem.

Expected

Won't work

Caused by HTML


Code Block
@priority=blocker
@issueType = bug



Code Block
@priority=blocker @issueType = bug


Code Block
@priority=blocker
 
@issueType = bug



Code Block
<div><span>@priority=blocker</span></div>
<div><span>@issueType = bug</span></div>
  • If DIV whitespace settings do not include whitespace Before or After, directives will be concatenated, breaking format

  • if DIV and SPAN whitespace settings include a Before or After, the DIV and SPAN newlines will add up, injecting an empty line, breaking format


Exporting from Audit History

...

Code Block
Content-Type: text/plain;
Content-Transfer-Encoding: base64
 
zNXewcDUIMfS0drO2cUgxMHOztnFIiAtIM7J1sUg0NLJ18/W1SDDydTB1NUgydog
zs/Xz8fPINcg18XS08nJIDguMy4xOg0KDQrywcLP1MEg0yDz9eLkLiD10NLB18zR
xc3ZxSDCzM/LydLP18vJLg0K8NLJINLBws/UxSDTmk1pY3Jvc29mdCBTUUwgU2Vy
dmVyINfF0tPJySAyMDA1IMkg19nbxSwgydPQz8zY2tXF1NPRINLF1snNINXQ0sHX

There is a base64 decode input box under the Regexp Tester, carefully paste that content to decode to underlying HTML:

...

editor action that is found within the Test Case editor, highlight the content and press Base64 Decode Selection:

...

Raising a support case

The tools are available to help you solve these problems yourself (faster). If you cannot do so, raise a support case, including:

  1. Your Profile XML (there is an export operation on the Profile list page for each profile)

  2. The email content from the JEMH Audit History or Test Case, attached as a file NOT PASTED!

Warning

.msg files from Outlook are not usable in any way and will be deleted on upload.

...

Filter by label (Content by label)
showSpaceevent listener jemh issue notification
showLabelsfalse
max5
spacesJEMH
falsesortmodified
typeshowSpacepagefalse
reversetruelabels
typepage
cqllabel in ( "directives" , "directive" , "field-processors" , "processor" , "processors" ) and space = "JEMH" and type = "page"
labelsevent listener jemh issue notification
Page Properties
hiddentrue


Related issues