---
title: "Update issues after initial issue creation"
canonical: "https://support.appfire.com/space/CW/69304376/Update%20issues%20after%20initial%20issue%20creation"
format: markdown
---
> Macro (aura-html)

# Description

The update issue transition post function can be used when issues are first created. This page explains the behavior of the post function before and after issue creation.

# Steps

1. Edit the intended workflow.
2. Click the *Open* step.
3. Click **Create** in the *Open *step.
  You are navigated to the *Create *transition screen.
4. Select the **Post Functions **tab.
5. Add the **Update Issues**<span style="color: #111111"> post function.</span>
6. <span style="color: #111111">Set parameters as you need.</span>
7. <span style="color: #111111">Move the post function below or above the </span><span style="color: #111111">*Creates the issue originally*</span><span style="color: #111111"> step depending on which issue fields you want to update in the issue. There is a difference in the way these issue fields are processed depending on the placement of </span><span style="color: #111111">*Update issues *</span><span style="color: #111111">with respect to the </span><span style="color: #111111">*Create the issue originally *</span><span style="color: #111111">step. Refer to the following table.</span>

| Issue field | Field updates when *Update issues *is added below *Create issue originally* | Field updates when *Update issues *is added above *Create issue originally* | Notes |
| --- | --- | --- | --- |
| Summary | :cross_mark: | :check_mark: |  |
| Description | :cross_mark: | :check_mark: |  |
| Priority | :cross_mark: | :check_mark: |  |
| Issue Type | :cross_mark: | :check_mark: |  |
| Environment | :cross_mark: | :check_mark: |  |
| Labels | :check_mark: | :cross_mark: |  |
| Assignee | :cross_mark: | :check_mark: |  |
| Reporter | :cross_mark: | :check_mark: |  |
| Due Date | :cross_mark: | :check_mark: |  |
| Original Estimates | :cross_mark: | :check_mark: |  |
| Remaining Estimates | :cross_mark: | :check_mark: |  |
| Watchers | :check_mark: | :cross_mark: |  |
| Fix Version  Versions | :cross_mark: | :cross_mark: |  |
| Affected Versions | :cross_mark: | :check_mark: |  |
| Create Link, Copy Remote Links, Copy Links | :check_mark: | :cross_mark: |  |
| Comments | :check_mark: | :cross_mark: |  |
| Attachments | :check_mark: | :check_mark: |  |
| Conditions | :check_mark: | :check_mark: |  |
| Issue security | :cross_mark: | :check_mark: |  |

For example, define the following issues fields as mentioned to avoid any unexpected behavior:

- The custom field in *Update issues *above the *Creates the issue originally *step is set with the mentioned format for the respective fields:
  - Set custom field: *Dev Due Date*
  - Value: *%original_created%*
  - Value 2: *3work*
- The *Due date *field in *Update issues *below the *Creates the issue originally *step is set with *Specific due date (%now%) with offset 5 work days*.

![image](media://d5097cfb-ed57-4a70-9a9a-ed12273df1b9)