We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-15297

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

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Email notifications
    • None
    • 9
    • 4
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? 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.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Data Center'
            1. Jira Data Center
            2. JRASERVER-15297

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

            XMLWordPrintable

              • Icon: Suggestion Suggestion
              • Resolution: Unresolved
              • None
              • Email notifications
              • None
              • 9
              • 4
              • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

                NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? 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.

                        Unassigned Unassigned
                        36b7953712a3 Paul Landolt
                        Votes:
                        80 Vote for this issue
                        Watchers:
                        54 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            36b7953712a3 Paul Landolt
                            Votes:
                            80 Vote for this issue
                            Watchers:
                            54 Start watching this issue

                              Created:
                              Updated: