Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

Overview

...

In some scenarios, if you have custom fields with the same name, then you have to use the ID of the custom field in the post function

This article explains how to copy two custom fields having the same name while using the Create on Transition - Create Issue post function. The solution suggests using the IDs of custom fields instead of names during workflow transition.

Instructions

Follow the below steps to update the post function with the custom field ID. 

  1. Log in to JIRA into Jira system as a Jira Administrator and Click on Cogwheel → Issues → click Image Added > Issues  > Fields (under Custom fields). 
  2. Navigate to the desired intended custom field and click on the cogwheel → Configure
  3. Image Removed

  4. You the Image Added Configure. You will be able to see the custom field ID in the address bar as shown in the following screen.
    Image Added
  5. Take a note of the custom field ID's IDs and navigate to the Workflow workflow associated with the project.
  6. Edit the respective Workflow and click on the Transition workflow as required.
  7. Select a transition which has the post function with the custom field values.
  8. Click on the Post functions tab and click on .
  9. Click the pencil icon.
  10. In the Create on Transition for JIRA – for Jira – Create issue(s), click on click Custom Fields in the left sidebar. 
  11. Now, start typing the custom field ID and select the custom field name in the "Copy original issue custom fields" field field.
  12. Once you select both the custom field names, it will look something like as shown below.Image Removed Image Removed:
    Image Added

     Image Added
  13. Click on Update and Publish publish the Workflow.
  14. Re-run the scenario and you will see notice that the custom fields with the same name are copied to the newly created issues.                  
Info

Test this in the

Dev

development instance before implementing in the production environment.