...
Field | Description/notes | Use in create | Use in comment | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
custom-field | the custom-field can be whatever the real custom field is called. If values for fields can be represented as a string, it will probably work. Tested with Labels, e.g. "Labels: sentByEmail" | ||||||||||
project | numeric (e.g. 10001), textual name (e.g. Support) or project key (e.g. SPP). Only required if email to: address is not a known project key | ||||||||||
priority | numeric (e.g. 4) or text name (e.g. critical) | ||||||||||
issueType | numeric (e.g. 12) or text name (e.g. Feature Request) Status
numeric (e.g. 6) or text name (e.g. Closed) It possible to migrate an existing Issue Type with a status by adding a comma separated id or name value of a given Status. For example (in the @ prefix field processor):
| ||||||||||
components | numeric (e.g. 100020) or textual name (e.g. My Magic Component) | ||||||||||
viewable | String value matching a group or role name, used to restrict the visibility of comments | ||||||||||
environment | String | ||||||||||
reporter | userid in JIRA | ||||||||||
assignee | userid in JIRA, who is 'assignable' | ||||||||||
summary | String (single line) | ||||||||||
description | String (multiple lines) | ||||||||||
watchers | Comma Separated Variable list of userid's, in Jira | ||||||||||
dueDate | Users can override the default (ISO standard) SimpleDateFormat string
| ||||||||||
workEstimate | of format 1w7d12h30m, or any derivative JIRA 6 requires spaces between values. When supplied in the subject it needs quoting like: | ||||||||||
linkto | Issue Linking, of format to:ABC-101/duplicate,from:XYZ-123/relates | ||||||||||
fixVersions | 1.3,2.1 | ||||||||||
affectsVersions | 1.0,1.1,2.0 | ||||||||||
vote | true (only value to make sense/false) | ||||||||||
securityLevel | Long value, e.g. 12345. Since 1.5.116/1.6.15 can be used on comment. |
...