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

Cannot clone a ticket when copying to a custom field when using a post function.

XMLWordPrintable

      Summary

      When attempting to Clone a ticket that includes copying from any field to a custom field using a post function, the error "We can't create this issue for you right now, it could be due to unsupported content you've entered into one or more of the issue fields. If this situation persists, contact your administrator as they'll be able to access more specific information in the log file." is shown in the UI.

      Steps to Reproduce

      1. Create a custom field with multi line text
      2. Create a post function in a workflow to copy from one any field to the custom field
      3. Execute workflow

      Expected Results

      Identified field's content is copied to the custom field.

      Actual Results

      The error We can't create this issue for you right now, it could be due to unsupported content you've entered into one or more of the issue fields. If this situation persists, contact your administrator as they'll be able to access more specific information in the log file. Is shown in the UI.

      Log files show:

      Unable to copy value from field 'Field Name' to 'Custom Field Name'.

      Note

      This same behaviour also occurs with Select list custom fields and possibly other fields types.

      logger:	 com.atlassian.jira.workflow.function.issue.CopyValueFromOtherFieldPostFunction

      Workaround

      Remove the post function for copying the value. 

          Form Name

            [JRACLOUD-78271] Cannot clone a ticket when copying to a custom field when using a post function.

            Matthew Hunter added a comment -
            Atlassian Update - January 26, 2023

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!
            Jira Cloud team

            Matthew Hunter added a comment - Atlassian Update - January 26, 2023 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team! Jira Cloud team

              Unassigned Unassigned
              2a6a615ea6bd Andy Launer
              Affected customers:
              1 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: