Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-15297

Add Conditions, Validators, Post Functions to the Clone, Edit operations

    • 106
    • 30
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Each Workflow step can have Conditions, Validators, or Post-Functions associated with them. Having these features associated with the Clone and Edit operations would allow easier manipulation and greater control of issues:

      • Associate a permission with the Clone permission to restrict who can clone on a per-project (or global) basis
      • Add a Clone post-function to delete certain fields that would be undesirable
      • Check the value of a certain field is populated after an edit (or process the field contents)

      In my particular use case, I wish to see a series of custom fields be cleared out when an Issue is cloned from another.

          Form Name

            [JRACLOUD-15297] Add Conditions, Validators, Post Functions to the Clone, Edit operations

            Any update on this? Would be really really helpful. 

            chandrakant ckz added a comment - Any update on this? Would be really really helpful. 

            Any update on this request?

            Pillai, Aarthi added a comment - Any update on this request?

            is it possible for you to share this script. I have a real nead to clear issue cloned because i have many specific field that have to ne eset .

            PARISATO Marie-Hélène added a comment - is it possible for you to share this script. I have a real nead to clear issue cloned because i have many specific field that have to ne eset .

            Rich Scire added a comment -

            I use ScriptRunner to clear fields when an issue is clone cloned. I assume that using global/project automation could do the same thing.

            Rich Scire added a comment - I use ScriptRunner to clear fields when an issue is clone cloned. I assume that using global/project automation could do the same thing.

            jodi.klein added a comment -

            This feature would be extremely helpful.  It would be great to be able to exclude fields from being cloned at the field level.  

            jodi.klein added a comment - This feature would be extremely helpful.  It would be great to be able to exclude fields from being cloned at the field level.  

            Floored this currently does not exist.

            I vote YES on implementing this feature. 

            Derek Lopez added a comment - Floored this currently does not exist. I vote YES on implementing this feature. 

            As futile as this seems, I definitely VOTE for this feature.  Since I have a couple of other requests that have been 'gathering interest' for many, many months, I am pessimistic of this happening.  However, I will hope for the best!  Thanks for the consideration!

            Trixie Johnson added a comment - As futile as this seems, I definitely VOTE for this feature.  Since I have a couple of other requests that have been 'gathering interest' for many, many months, I am pessimistic of this happening.  However, I will hope for the best!  Thanks for the consideration!

            This would be immensely useful to make sure our controls we have in place (gates for custom field validations) are adhered to.

            Warren Kent added a comment - This would be immensely useful to make sure our controls we have in place (gates for custom field validations) are adhered to.

            Implementing this functionality would be greatly appreciated by all Jira administrators. Please get it done.

            Gregory Kremer added a comment - Implementing this functionality would be greatly appreciated by all Jira administrators. Please get it done.

            Kent Chiu added a comment -

            We also need the ability to Clone regardless of the CREATE workflow condition.  We have implemented some conditions in the CREATE workflow to enforce the provision of information in some of the fields.  Currently, Cloning is unable for projects that have imposed field requirements for the issue creation. At least provide a pre Clone screen to allow user to update the fields required in the ticket to proceed.

            Kent Chiu added a comment - We also need the ability to Clone regardless of the CREATE workflow condition.  We have implemented some conditions in the CREATE workflow to enforce the provision of information in some of the fields.  Currently, Cloning is unable for projects that have imposed field requirements for the issue creation. At least provide a pre Clone screen to allow user to update the fields required in the ticket to proceed.

              Unassigned Unassigned
              36b7953712a3 Paul Landolt
              Votes:
              152 Vote for this issue
              Watchers:
              85 Start watching this issue

                Created:
                Updated: