Versions Compared

Key

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

...

...

...

...

...

...

...

Whenever multiple issue creation is configured for 'creation on a transition' the Creation on Transition post function and the same transition occurs after the reopening of the issue, the post function will execute again and will create is run again resulting in duplicate issues. This article explains on how explains how to restrict the creation of duplicate issues when the issue is reopened.

Instructions

  1. Log into Jira as a Jira Administrator and click Image Modified > Issues  > Projects.
  2. Navigate to the intended project and Click on click Project Settings > Click on target Workflowintended workflow.
  3. Click on target the transition where for which Create on Transition is configured. 
    Let's assume below is the a sample post function configured for Creation creation of multiple issues for Custom custom field value selection. Please see the page refer to How to create multiple issues for reference.Post FunctionImage Removed                 Click On more information.
    Post FunctionImage Added
  4. Click  to edit the Create Issue Post  post function
     Image RemovedImage Added 
  5. Click On Conditions and Configurations section available Select the Conditions & Configuration tab on the left navigation panel.
  6. Write a Enter the below mentioned JQL in JQL query field.

    Image Added
    The query checks whether the original issue was in closed status or not.  Image Removed 

    Tip
    iconfalse

    issue = %original_key% AND Status was in (Closed)


  7. Add the below mentioned condition and for the issues will to be created only when below the condition is true.met:
      Image RemovedImage Added
  8. Update the configuration and the updated post function looks like below.:
     Image RemovedImage Added

  9. Publish the workflow before executing the transition. You will be able to see that no duplicate issues will be are created when the same transition occurs post reopen of after reopening the issue.
Info

The suggestion It is recommend to test this scenario in a test environment before implementing the same in the production.