---
title: "Issue fields - Cloud"
canonical: "https://support.appfire.com/space/CSOT/68748372/Issue%20fields%20-%20Cloud"
format: markdown
---
> Macro (aura-html)
# Description
Create Issue, Update Issues, and Create Subtask post functions support a number of fields for a configuration that helps you control when the issue or subtask should be created or updated and what information is associated with the issue or subtask once created or updated.
> ✅ ### Important Notes
> ✅
> ✅ - If the issue is not a subtask, then the Parent Issue is the same as the Original Issue (the issue that originally started the transition).
> ✅ - Unless otherwise indicated, most fields are common to Create Issue, Create Subtask and Update Issues.
# Sections containing field configurations
The configuration screen contains sections of powerful configuration options.
> ℹ️ On the top right corner of any selectable field, when you hover over you can see usable icons that help you switch between one of the following modes:
> ℹ️
> ℹ️ - Select value (default) - select a value from the available list of options or type in the field to select a value from the auto-suggestions
> ℹ️ - Set value - enter a value as required from the [Substitution variables](https://appfire.atlassian.net/wiki/spaces/CSOT/pages/68749234) list
## Basic fields
The following configuration fields are most commonly used by customers.
| Field | Create Issue
(Available) | Create Subtask
(Available) | Update Issues (Available) | Default | Description |
| --- | --- | --- | --- | --- | --- |
| Summary | :check_mark: | :check_mark: | :check_mark: | - Original summary (Create issue)
- Parent summary (Create subtask)
- Same (Update Issues) | Enter a summary for the issue being created or updated. Alternatively, you can add substitution variables to copy the summary from the parent or original issue. The character limit for this field is a maximum of 255 characters.
> ❌ Ensure the summary entry respects the character limit. If not, the post function cannot be processed further. |
| Description | :check_mark: | :check_mark: | :check_mark: | Same (Update Issues) | Enter a detailed description for the issue being created or updated. |
| Environment | :check_mark: | :check_mark: | :check_mark: | Same (Update Issues) | Enter the hardware and software environment details related to the issue (if applicable). |
| Notes | :check_mark: | :check_mark: | :check_mark: | | Enter additional notes you may want to add with the post function. |
## Detailed fields
Configurations within this section help direct where new issues or subtasks are created or updated, who they are assigned, and other important details associated with the issue and subtask creation.
| Field | Create Issue
(Available) | Create Subtask
(Available) | Update Issues (Available) | Default | Description |
| --- | --- | --- | --- | --- | --- |
| Projects | :check_mark: | :cross_mark: | :cross_mark: | Original project | Lists all the available projects. Select one or more projects from the list to create issue(s) in the specified project(s) or start typing in the field to select a project from the respective auto-suggestions. Alternatively, you can enter substitution variables by switching to the *Set value* mode.
The other issue field values displayed in the form are dependent on this selection. For example, when one project is selected, *Issue type *displays only the respective issue types. When multiple projects are selected, it displays all issue types from all the projects in the instance. |
| Entry Parent | :cross_mark: | :check_mark: | :cross_mark: | Parent issue key | Lists all the available issues in the instance. Select one or more issues to create subtask(s) in the specified issue(s) or start typing in the field to select an issue from the respective auto-suggestions. Alternatively, you can enter substitution variables by switching to the *Set value* mode.
> ℹ️ If you do not find the intended issue key(s) in the auto-suggestions list associated with this field, you can:
> ℹ️
> ℹ️ 1. Switch to the *Set value *mode.
> ℹ️ 2. Enter the issue key of the issue you want to update. For example, *KEY-1 *or *%original_key%.*
> ℹ️ Or
> ℹ️ Enter all the intended issue keys separated by a comma to update more than one issue. For example:
> ℹ️ - KEY-1, KEY-10, KEY-12
> ℹ️ - KEY-1, %original_key%, KEY-12, %parent_key%
> ℹ️ - %original_key%, %parent_key%
> ℹ️
> ℹ️ You can also use any substitution variable that returns issue key value such as %jql_result_1%, etc., to define issue keys. |
| Issues to update | :cross_mark: | :cross_mark: | :check_mark: | Original key | Start typing in the field to view the respective list of auto-suggestions. From this list, select one or more issues to be updated with the configuration provided. You can also set values using substitution variables by switching to the *Set value* mode.
> ℹ️ If you do not find the intended issue key(s) in the auto-suggestions list associated with this field, you can:
> ℹ️
> ℹ️ 1. Switch to the *Set value *mode.
> ℹ️ 2. Enter the issue key of the issue you want to update. For example, *KEY-1 *or *%original_key%.*
> ℹ️ Or
> ℹ️ Enter all the intended issue keys separated by a comma to update more than one issue. For example,
> ℹ️ - KEY-1, KEY-10, KEY-12
> ℹ️ - KEY-1, %original_key%, KEY-12, %parent_key%
> ℹ️ - %original_key%, %parent_key%
> ℹ️
> ℹ️ You can also use any substitution variable that returns issue key value such as %jql_result_1%, etc., to define issue keys. |
| Issue type | :check_mark: | :check_mark: | :check_mark: | - Bug or Subtask
- Same (Update Issues) | The issue types listed here are dependent on how the *Project *field is set.
- If set using *Select value *mode: This field lists all the issue types present in the project specified in the *Project *field.
- If set using *Set value* mode (Substitution variables): This field lists all the issue types present across all projects.
Select a value from the list to set the issue type of the issue being created or updated. Alternatively, you can add substitution variables by switching to the *Set value* mode.
> ℹ️ The issue types are categorized under:
> ℹ️
> ℹ️ A. *CLASSIC ISSUE TYPES*: Most of the issue types in classic projects are common across projects. They are displayed as is.
> ℹ️
> ℹ️ B. *NEXT-GEN ISSUE TYPES*: You may see one or more issue types repeated multiple times in the list. To differentiate these issue types and select one that suits your requirement, you see the project key in the brackets next to each issue type.
> ℹ️
> ℹ️ Refer to the following image:
> ℹ️
> ℹ️ 
> ℹ️
> ℹ️ You also have:
> ℹ️
> ℹ️ - *Parent project *and *Entry project *as other options to select from in *Create issue.*
> ℹ️ - *Parent's issue type *and* Original issue type *as other options to select from in *Create subtask *and *Update* *issue.* |
| Transition | :cross_mark: | :cross_mark: | :check_mark: | | Enter transition name or ID. During transition, only fields available on the transition screen are updated. The original issue being transitioned can not be a part of another transition. Refer to [Transition Issues](https://appfire.atlassian.net/wiki/spaces/CSOT/pages/68748996). |
| Priority | :check_mark: | :check_mark: | :check_mark: | - Parent's priority
- Same (Update Issues) | Lists all the available priorities. Select a priority from the list or start typing in the field to select a value from the respective auto-suggestions to set the priority of the issue being created or updated over other issues. Alternatively, you can set values using substitution variables by switching to the *Set value* mode.
Notice that the existing list displays the *Parent's priority* and *original priority* options, which can also be set using substitution variables. |
| Components | :check_mark: | :check_mark: | :check_mark: | - Parent issue's components
- Same (Update Issues) | Set components to which the issue being created or updated is related to. Start typing in the field to view the respective list of auto-suggestions. Select a component from the list. Alternatively, you can set values using substitution variables by switching to the *Set value* mode. |
| Affected versions | :check_mark: | :check_mark: | :check_mark: | Same (Update Issues) | Set the project version to which the issue being created or updated is a part of. You can set a value by selecting a value from the existing list or using substitution variables by switching to the *Set value* mode.
Notice that the values like *Parent issue's affected versions *and *Parent issue's fixed versions* are present in the list for you to select from or can be set using substitution variables. |
| Fixed versions | :check_mark: | :check_mark: | :check_mark: | Same (Update Issues) | Set the project version in which the issue being created or updated is being fixed. You can set a value by selecting a value from the existing list or using substitution variables by switching to the *Set value* mode.
Notice that the values like *Parent issue's fixed versions *and *Parent issue's fixed versions* are present in the list for you to select from or can be set using substitution variables. |
| Security level | :check_mark: | :cross_mark: | :check_mark: | - None
- Same (Update Issues) | Set permissions that determine which users, groups, or project roles have access to the issue being created or updated. You can set security level by selecting a value from the existing list or using substitution variables by switching to the *Set value* mode.
Notice that the values like *Parent issue's security level *and *Original issue's security level * are present in the list for you to select from or can be set using substitution variables. |
| Labels | :check_mark: | :check_mark: | :check_mark: | Same (Update Issues) | Lists all the available labels. You can either select from the list available to set values for the issue being created or updated or start typing in the field to select a value from the respective auto-suggestions. Alternatively, you can set values using substitution variables by switching to the *Set value* mode.
Notice that the values like *Parent issue's label *and *Original issue's label* are present in the list for you to select from or can be set using substitution variables. |
| **People** |
| Reporter | :check_mark: | :check_mark: | :check_mark: | - Current user
- Same (Update Issues) | Set the user whom you want to be the creator of the issue being created or updated. You can select a user from the list available or start typing in the field to select a value from the respective auto-suggestions. Alternatively, you can set values using substitution variables by switching to the *Set value* mode.
Notice that the following values are present in the list for you to select from or can be set using substitution variables:
- Current user
- Original issue's reporter
- Original issue's assignee
- Parent issue's reporter
- Parent issue's assignee
- Project lead |
| Assignee | :check_mark: | :check_mark: | :check_mark: | - Parent issue's assignee
- Same (Update Issues) | Set the user to whom you want to assign the issue being created or updated. You can select a user from the list available or start typing in the field to select a value from the respective auto-suggestions. Alternatively, you can set values using substitution variables by switching to the *Set value* mode.
Notice that the following values are present in the list for you to select from or can be set using substitution variables:
- Current user
- Original issue's reporter
- Original issue's assignee
- Parent issue's reporter
- Parent issue's assignee
- Project lead
- Unassigned
- Automatic |
| Watchers | :check_mark: | :check_mark: | :check_mark: | Same (Update Issues) | Add one or more users as watchers to the issue being created or updated. You can select user(s) from the list available or start typing in the field to select the user from the respective auto-suggestions.
Notice that the values like *Original issue's watchers* and *Parent issue watcher* are present in the list for you to select from or can be set using substitution variables. |
| **Dates** |
| Due date | :check_mark: | :check_mark: | :check_mark: | Same (Update Issues) | Set a due date by which you want the issue being created or updated complete. Enter a specific date in the field or select from the list available. Alternatively, you can set values using substitution variables by switching to the *Set value* mode.
*dd/MMM/yy* is the only valid date format to be used when you enter a specific date. For example, 29/Mar/20. |
| Original Estimate | :check_mark: | :check_mark: | :check_mark: | Same (Update Issues) | Set the original estimate, which is the amount of time required to resolve the issue being created or updated. Enter a value in the field in a valid format. For example, *2w 1d 6h 30m *or *7d 2h 40m*.
- w - weeks
- d - days
- h - hours
- m - minutes |
| Remaining estimate | :check_mark: | :check_mark: | :check_mark: | Same (Update Issues) | Set remaining estimate, which is the current estimate of remaining amount of time required to resolve the issue being created or updated. Enter a value in the field in a valid format. For example, *1w 3d 10h 30m*.
- w - weeks
- d - days
- h - hours
- m - minutes |
## Links
Configurations within this section help create and copy links and link types.
| Field | Create Issue
(Available) | Create Subtask
(Available) | Update Issues (Available) | Default | Description |
| --- | --- | --- | --- | --- | --- |
| **Create links** |
| Issue(s) | :check_mark: | :check_mark: | :check_mark: | | Add one or more issue keys to link to the issue being created or updated to the specified issues. Start typing in the field to select one or more issues from the respective auto-suggestions. Alternatively, you can set values using substitution variables by switching to the *Set value* mode.
> ℹ️ If you do not find the intended issue key(s) in the auto-suggestions list associated with this field, you can:
> ℹ️
> ℹ️ 1. Switch to the *Set value *mode.
> ℹ️ 2. Enter the issue key of the issue you want to update. For example, *KEY-1 *or *%original_key%.*
> ℹ️ Or
> ℹ️ Enter all the intended issue keys separated by a comma to update more than one issue. For example,
> ℹ️ - KEY-1, KEY-10, KEY-12
> ℹ️ - KEY-1, %original_key%, KEY-12, %parent_key%
> ℹ️ - %original_key%, %parent_key%
> ℹ️
> ℹ️ You can also use any substitution variable that returns issue key value such as %jql_result_1%, etc., to define issue keys.
> ⚠️ - Values like *Parent issue key* and *Original key* are present in the list for you to select from or can be set using substitution variables.
> ⚠️ - Recently viewed issues by the user configuring the post function, are displayed at the top of the list for convenience. |
| Link type | :check_mark: | :check_mark: | :check_mark: | | Lists all the link types. Select the link type of the issue links added in the *Issue(s) *field from the available list or set a value using substitution variables by switching to the *Set value* mode. |
| Link direction | :check_mark: | :check_mark: | :check_mark: | | Select a value for the link direction from the available list or start typing in the field to select a value from the respective list of auto-suggestions. This specifies if the link associated is inwards (target to source) or outwards (source to target). |
| **Copy links** |
| Issue(s) | :check_mark: | :check_mark: | :check_mark: | | Add one or more issue keys to copy the respective issue links to the issue being created or updated. Start typing in the field to select one or more issues from the respective auto-suggestions. Alternatively, you can set values using substitution variables by switching to the *Set value* mode.
By default, all link types are copied from each issue key specified. To copy links of specific link types, select the required link type from the *Link types *field.
> ℹ️ If you do not find the intended issue key(s) in the auto-suggestions list associated with this field, you can:
> ℹ️
> ℹ️ 1. Switch to the *Set value *mode.
> ℹ️ 2. Enter the issue key of the issue you want to update. For example, *KEY-1 *or *%original_key%.*
> ℹ️ Or
> ℹ️ Enter all the intended issue keys separated by a comma to update more than one issue. For example,
> ℹ️ - KEY-1, KEY-10, KEY-12
> ℹ️ - KEY-1, %original_key%, KEY-12, %parent_key%
> ℹ️ - %original_key%, %parent_key%
> ℹ️
> ℹ️ You can also use any substitution variable that returns issue key value such as %jql_result_1%, etc., to define issue keys.
> ⚠️ You cannot copy links while creating multiple issues or subtasks. |
| Link types | :check_mark: | :check_mark: | :check_mark: | | Lists all the link types. Select one or more link types from the list to copy only the link(s) with specified link type(s) to the issue being created or updated. Alternatively, you can set values using substitution variables by switching to the *Set value* mode. |
| **Copy remote links** |
| Issue(s) | :check_mark: | :check_mark: | :check_mark: | | Add one or more issue keys to copy the respective remote links to the issue being created or updated. Start typing in the field to select one or more issues from the respective auto-suggestions. Alternatively, you can set values using substitution variables by switching to the *Set value* mode.
By default, all remote link types are copied from each issue key specified.
> ℹ️ If you do not find the intended issue key(s) in the auto-suggestions list associated with this field, you can:
> ℹ️
> ℹ️ 1. Switch to the *Set value *mode.
> ℹ️ 2. Enter the issue key of the issue you want to update. For example, *KEY-1 *or *%original_key%.*
> ℹ️ Or
> ℹ️ Enter all the intended issue keys separated by a comma to update more than one issue. For example,
> ℹ️ - KEY-1, KEY-10, KEY-12
> ℹ️ - KEY-1, %original_key%, KEY-12, %parent_key%
> ℹ️ - %original_key%, %parent_key%
> ℹ️
> ℹ️ You can also use any substitution variable that returns issue key value such as %jql_result_1%, etc., to define issue keys.
> ⚠️ Note that all the Confluence links of the specified *Issue(s) *are copied as weblinks. |
## Comment & attachments
This section allows you to control whether or not to associate attachments from the parent or other Issues during creation. You also have similar controls around comments.
| Field | Create Issue
(Available) | Create Subtask
(Available) | Update Issues (Available) | Default | Description |
| --- | --- | --- | --- | --- | --- |
| **Comments** |
| Add comment | :check_mark: | :check_mark: | :check_mark: | | Enter some helpful text to be associated with the issue being created or updated. Use [substitution variables](https://appfire.atlassian.net/wiki/pages/createpage.action?spaceKey=csot&title=Substitution%20variables%20-%207.x&linkCreation=true&fromPageId=68748372) to customize a comment in addition to free text. |
| Comment security | :check_mark: | :check_mark: | :check_mark: | None | Select the group of users to whom you want the comment to be visible for the issue being created or updated. |
| Copy parent issue comments | :check_mark: | :check_mark: | :check_mark: | Off | Enable (On) this toggle to copy the comments from the parent of the issue that is being transitioned to the issue being created or updated.
> ℹ️ When you use this option, note that the original commentator is replaced with the user performing the transition or acting user, if configured.
> ⚠️ When the parent issue comments contain embedded media such as an image or GIF etc., you see a broken image in the *Comments* section of the issue being created or updated. |
| Copy original issue comments | :check_mark: | :check_mark: | :check_mark: | Off | Enable (On) this toggle to copy the comments from the issue that is being transitioned to the issue being created or updated.
> ℹ️ - When you add a comment using one or more given options i.e., *Add comment*, *Copy parent issue comments*, and *Copy original issue comments, *all the respective comments are copied to the issue being created or updated.
> ℹ️ - When you use this option, note that the original commentator is replaced with the user performing the transition or acting user, if configured.
> ⚠️ When the original issue comments contain embedded media such as an image or GIF etc., you see a broken image in the *Comments* section of the issue being created or updated. |
| **Attachments** |
| Copy attachments | :check_mark: | :check_mark: | :check_mark: | | Start typing in the field to select one or more issues from the respective auto-suggestions to copy the respective issues' attachment(s) to the issue being created or updated. Alternatively, you can set values using substitution variables by switching to the *Set value* mode.
> ℹ️ If you do not find the intended issue key(s) in the auto-suggestions list associated with this field, you can:
> ℹ️
> ℹ️ 1. Switch to the *Set value *mode.
> ℹ️ 2. Enter the issue key of the issue you want to update. For example, *KEY-1 *or *%original_key%.*
> ℹ️ Or
> ℹ️ Enter all the intended issue keys separated by a comma to update more than one issue. For example,
> ℹ️ - KEY-1, KEY-10, KEY-12
> ℹ️ - KEY-1, %original_key%, KEY-12, %parent_key%
> ℹ️ - %original_key%, %parent_key%
> ℹ️
> ℹ️ You can also use any substitution variable that returns issue key value such as %jql_result_1%, etc., to define issue keys.
> ⚠️ You cannot copy attachments while creating multiple issues or subtasks. |
## Custom fields
Configuration settings within this section allow you to:
- copy custom field values from the parent or original issue
- define values for new custom fields
> ⚠️ If the custom fields are not selected in this section, all the custom field values are copied from the original or parent issue.
| Field | Create Issue
(Available) | Create Subtask
(Available) | Update Issues (Available) | Default | Description |
| --- | --- | --- | --- | --- | --- |
| Copy original issue custom fields | :check_mark: | :check_mark: | :check_mark: | | Lists all the custom fields of the original issue. Select one or more values to copy them to the issue being created or updated. Alternatively, you can set values using substitution variables by switching to the *Set value* mode. |
| Copy parent issue custom fields | :check_mark: | :check_mark: | :check_mark: | | Lists all the custom fields of the parent issue. Select one or more values to copy them to the issue being created or updated. Alternatively, you can set values using substitution variables by switching to the *Set value* mode. |
| Add Custom Field | :check_mark: | :check_mark: | :check_mark: | | Click **+ Add custom field **to define and add new custom fields for the issue being created or updated. You can leave a custom field *Value *empty, if you want to clear the respective value in the issue being created or updated.
> ⚠️ For a *Sprint *custom field:
> ⚠️
> ⚠️ - only when the parent/original issue is assigned to one or more sprints, you can set those sprints as sprint values using the *Add Custom Field *option.
> ⚠️ - when the parent/original issue is not assigned to any sprint, you cannot set any sprint value.
> ⚠️
> ⚠️ To know how to set a sprint field value as parent/original issue, refer to [Substitution variables](https://appfire.atlassian.net/wiki/spaces/CSOT/pages/68749234). |