---
title: "Setting fields"
canonical: "https://support.appfire.com/space/JCPP/71272885/Setting%20fields"
format: markdown
---
> Macro (aura-html)

### Summary

When customizing operations, you can set specific fields. The following indicates what fields are available for modification. For values, you can use text or [Substitution variables](https://appfire.atlassian.net/wiki/spaces/JCPP/pages/71274446) or a combination of both. If you have a need for additional fields, [raise a support request](https://appf.re/support) with our support team.. The general format for setting a field is **.set.** or **.set.subtask.** with the custom number as a prefix and the field name to be set as the postfix. Main issue fields are controlled by **.set.** and subtasks copied as a result of cloning the main issue are set using **.set.subtask.**

| **Field Name** | **Notes and Examples** |
| --- | --- |
| summary | `1.set.summary = Clone - %original_summary%` |
| description | `1.set.description = %original_description%` |
| environment | `1.set.environment = %original_environment%` |
| issuetype | # This can set **subtask** issue type only. See [Clone properties](https://appfire.atlassian.net/l/cp/sv0N0dqj) for discussion of setting the project and issue type of the cloned issue.<br>`1.set.subtask.issuetype = Documentation subtask`<br>`1.set.subtask.issuetype = 19` |
| priority | `1.set.priority = 1` |
| Assignee | `1.set.assignee = bob` |
| Special Value | Example |
| unassigned | `1.set.assignee =` |
| current user | `1.set.assignee = %user_id%` |
| automatic_assignee | `1.set.assignee = %entry_automatic_assignee%` |
| project_lead | `1.set.assignee = %entry_project_lead%` |
| reporter | `1.set.reporter = bob` |
| components | `1.set.components = C1, C2` |
| labels | `1.set.labels = label1 label2`<br>> ℹ️ It is recommended to include the required labels in the **ignoreFields** or **fieldExcludes** (refer to [Clone properties](https://appfire.atlassian.net/l/cp/sv0N0dqj)) list, for them to behave as expected during Clone operations. |
| security | `1.set.security = Developers` |
| Special Value | Example |
| Project default | `1.set.security = %entry_project_default security%` |
| affectsVersions | `1.set.affectsVersions =` |
| fixVersions | `1.set.fixVersions = V2, V1` |
| duedate | # Format: d/MMM/yy - but any JIRA application property format should work<br>`3.set.duedate = 13/Sep/17` |
| originalEstimate | # Time duration format - note, for **ignoreField** use, you will need to add **timetracking** as the field name to ignore<br>`1.set.originalEstimate = 3h 30m` |
| remainingEstimate | # Time duration format<br>`1.plus.set.remainingEstimate = 3d`<br>To copy original estimate using substitution variable, use -<br>`1.plus.set.remainingEstimate = %parent_original_estimate%`<br>> ℹ️ When remaining estimate is not set, the *original estimate* is considered as remaining estimate. |
| comment | # Custom comment can be added as a part of cloning operation<br>`1.plus.set.comment =` "*<Any custom comment you may wish to add to the cloned issue>*"<br>Example -<br>`1.plus.set.comment = `"The comments above belong to the parent issue" |
| custom fields | # Note that blanks must be escaped in custom field names<br>`1.set.custom\ three = %original_assignee%`<br>`1.set.custom-multi-select = s2,s1, s3`<br>`1.set.custom-cascade-select = 1,A`<br>`1.set.customfield_10010 = test + %original_summary%`<br>`1.set.custom-date-type-field = %now%`<br>> ℹ️ - If your project consists of custom fields, it is recommended to include them in the **ignoreFields** (refer to [Clone properties](https://appfire.atlassian.net/l/cp/sv0N0dqj)) list, for them to behave as expected during clone operations.
> ℹ️ - The set field value takes the precedence over the cloned value when you clone a field. |