Table of Contents |
---|
...
Directive | On Create | On Comment | Notes |
---|---|---|---|
summary | Replaces existing summary | ||
reporter | Replaces both from address and profile's default reporter | ||
emailSenderAsUser | Not supported yet | Not supported yet | |
assignee | Replaces profile's default, If the assignee is not assignable, the message will be rejected | ||
issueType | Issue type is specially important because the metadata depends on it. If not valid for the project, the message will be rejected | ||
issueKey | N/A, JEMH will comment the issue if it exists | Yes, changes issue to be commented/updated taking precedence over the issue key in subject, mime header threading and the associated issue to the mime message id. Equality condition and custom JQL are supported (1.0.86+), JEMHC resolves the first not resolved issue that matches the criteria. Examples:
| |
parentIssueKey | Possible UC could be replying to a subtask issue with @parentIssueKey changing the parent. For some reason, JIRA is not updating subtask's parent through REST. | See https://answers.atlassian.com/questions/9374899/can-i-change-sub-task-parent-using-rest | |
labels | csv splitting the field processor value, not taking in consideration any escaping Label values are 'set' not 'added'. Currently overrides the 'profile' labels (should we merge?) | ||
priority | |||
description | Replaces the post processed body of the email | ||
comment | Create: Adds the directive's value as a comment after the issue has been created. Comment: Uses as body of the comment replacing the body of the post processed email | ||
components | Yes - Set | Yes - Update | Not escaped CSV. If one of components in the list is invalid, it will be ignored (with reporting) |
project | Yes - It changes where the issue will be created ignoring the project key in profile | Yes but it just used as validation. Comment fails if the resolved issue key doesn't belongs to the project | Project is also important as metadata depends on it. Validation in UI can fail during processing. e.g: some custom fields or issue type is not available in the directive's project |
dueDate | |||
reuqesttyperequestType | Not possible to change | Service Desk’s request type. Name or id can be provided. Example: | |
dueDateFormat | Replaces profile's default due date | ||
Epic Label |
| It set the epic label of the create or updated issue only if the issue is of type Epic @Epic Label=The Epic Label | |
Epic Link | Value can be either the key or the label of the target epic. @Epic Link=SCRUM-123 @Epic Link=The Epic Label | ||
Sprint |
| it assigns the issue to a sprint. @Sprint=6 (Sprint with id 6) @Sprint=Board Name:Sprint Name @Sprint=Board Name (Active sprint in board 'Board Name') | |
watchers |
|
| @watchers=someJiraUserName, someJiraUserEmail@myCompany.com |
viewable | Not supported yet | Not supported yet | |
ccusers | Not supported yet | Not supported yet | |
workEstimate | Not supported yet | Not supported yet | |
environment | Yes - Set | ||
linkto | Not supported yet | Not supported yet | |
affectsVersions | Not escaped CSV. If one of versions in the list is invalid, it will be ignored (with reporting). 'affectsVersions' is actually the 'version' field labeled 'Affected Versions' in UI. | ||
fixVersions | Not escaped CSV. If one of versions in the list is invalid, it will be ignored (with reporting). | ||
vote | Not supported yet | Not supported yet | |
logWorkDone | Not supported yet | Not supported yet | |
securityLevel | - Set | - Update | The field name is 'security' |
|
|
| Attachment is not a field |
|
|
| |
Worklog directives | Not supported yet | Not supported yet | All the directives related to worklog |
notifyOnEdit | Not supported yet | Not supported yet | |
workflow | Resolution defaults to Fixed. Only One transition permitted (so far). Basic version. The transition is applied after everything else: update issue, comment issue, upload attachments workflow:Start Progress @workflow=Close Issue | ||
workflow.resolution | Resolution is set if it's allowed in the transition, e.g. workflow:Close Issue workflow.resolution=Duplicate | ||
workflow.params | A worklow field is set if it is allowed in the transition or it is allowed in the issue after the transition has been applied. workflow.params.description:The description applied during or after the transition workflow.params.customfield_10001:Custom Field Value | ||
|
|
| |
custom fields | Set overriding default custom field values but not the custom fields used for email only users | Update (including custom fields used for email only users) | |
internalComment | if there is a @comment directive | if the issue is a JSD issue, @internalComment=true/yes (case insensitive) marks the created comment as JSD internal. Otherwise @internalComment=* marks the comment as public (shared with customer). The directive overrides the Project Mapping's 'Service Desk Comment Mode' configuration. It is a good idea to create @internal @public aliases from @internalComent=true/false respectively. |
JEMHCloud is trying to do the best possible to pre-validate every processor before send it to jira. E:G: if the priority is invalid, it will be ignored reporting the invalid value.
...
You can use either field name (case insensitive) or field id (like customfield_10001) as directive key. Multiple values are comma separated.
...