Supported fields and custom fields
Difference between Replace and Append
Replace removes the old value and save a value taken from the source issue. Append adds selection to existing value (if possible).
System fields
| Name | Type |
|---|---|
| Assignee | |
| Attachments | Append |
| Comments | Append |
| Description | Specified format |
| Due date | |
| Issue links | |
| Labels | Append and Replace |
| Priority | |
| Reporter | |
| Security | |
| Subtasks | |
| Summary | |
| Votes | Append and Replace |
| Watchers | Append and Replace |
| Worklog |
Custom fields
| Name or type | |
|---|---|
| Radio buttons | |
| Single, Multi and Checkbox Select | |
| Single and Multiline text field |
Jira Software
| Name | |
|---|---|
| Epic color | |
| Epic link | |
| Epic name | |
| Epic status | |
| Development | |
| Sprint | |
| Rank | |
| Story points |
Jira Service Management
| Name | |
|---|---|
| Approvals | |
| Approvers | |
| Customer Request Type | |
| Organizations | |
| Request | |
| Satisfaction | |
| Satisfaction date | |
| Time to first response | |
| Time to resolution | |
| Request Participants | Append and Replace |
| Customer Request Type |
Info
Don’t you see an interesting field / custom field on the list? Contact us and we’ll add support (if it’s technically possible).
Also, there are two options in the global settings connected with Jira Service Management:
- Merge comments into public
- Add reporter to the participants list