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

When cloning an issue, if a text field has a Table with Markup content, it breaks the clone's format

      Issue Summary

      When cloning an issue, if a text field (e.g. Description), has a Table with a Heading Markup Format written inside the column or row, the cloned issue will be created without the proper format, breaking the Table.

      Steps to Reproduce

      1. Create an issue
      2. Add a Table to a description field, and add text with Heading Format (e.g. Heading 1, 2, 3, 4, 5, or 6)
      3. Save the changes
      4. Clone the issue from ... -> Clone

      Expected Results

      The issue should be cloned successfully, with the proper information and correct format (table + heading format).

      Actual Results

      The issue is cloned, however, the table is broken, with the Heading Markup format apart from the original table. Please mind the following screenshot.

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

            [JRACLOUD-81240] When cloning an issue, if a text field has a Table with Markup content, it breaks the clone's format

            Anusha Rutnam added a comment - - edited

            From closed duplicate JRACLOUD-80234 – Table option Header row for Table in the issue description is not copied while cloning the issue

            Issue Summary

            When having a table in the issue description that has inside its cell a line of text followed by an extra space and a bullet list, the cloning process fails.

            Steps to Reproduce

            • Create an issue
            • Create a table within the description
            • In all of its cells, write single-word text and add Table option Header row.
            • Clone the issue

            Expected Results

            The issue will be cloned successfully.

            Actual Results

            The cloning process is successful, however, in cloned issue, the table is not copied.

            Anusha Rutnam added a comment - - edited From closed duplicate JRACLOUD-80234 – Table option Header row for Table in the issue description is not copied while cloning the issue Issue Summary When having a table in the issue description that has inside its cell a line of text followed by an extra space and a bullet list, the cloning process fails. Steps to Reproduce Create an issue Create a table within the description In all of its cells, write single-word text and add Table option Header row . Clone the issue Expected Results The issue will be cloned successfully. Actual Results The cloning process is successful, however, in cloned issue, the table is not copied.

            From closed duplicate JRACLOUD-81887 – Table cell with bullet list and extra line breaks in the issue description results in incorrect description format in cloned issue

            Issue Summary

            Table cell with bullet list and extra line breaks in the issue description results in incorrect description format in the cloned issue.

            Steps to Reproduce

            1. Create an issue
            2. Create a table within the description
            3. In one of its cells, add bullet list
            4. Add a few line breaks after the last bullet list
            5. Clone the issue

            Expected Results

            The issue will be cloned successfully.

            Actual Results

            The cloned issue description format changes.

            Workaround

            Currently, there is no known workaround for this behaviour. A workaround will be added here when available.
            The content has to be copied manually from the source issue.

            Anusha Rutnam added a comment - From closed duplicate JRACLOUD-81887 – Table cell with bullet list and extra line breaks in the issue description results in incorrect description format in cloned issue Issue Summary Table cell with bullet list and extra line breaks in the issue description results in incorrect description format in the cloned issue. Steps to Reproduce Create an issue Create a table within the description In one of its cells, add bullet list Add a few line breaks after the last bullet list Clone the issue Expected Results The issue will be cloned successfully. Actual Results The cloned issue description format changes. Workaround Currently, there is no known workaround for this behaviour. A workaround will be added here when available. The content has to be copied manually from the source issue.

            From closed duplicate JRACLOUD-81028 – Number list in the table description changes the format while cloning the issue

            Issue Summary

            Cloning is changing the table format if the table description has a numbering list.

            Steps to Reproduce

            1. Create an issue(I tried task issue type).

            2. Create a table in the description and use the following in one of the columns.

            1. test1

            2. test2

            3. test3

            3. Clone the issue.

            Attaching the Screen Recording.

            Expected Results

            The table is cloned as it is.

            Actual Results

            The table format changes in the cloned issue.

            Workaround

            There are a couple of workarounds.

            1. Try the following format

            1 - test1
            2 - test2
            3 - test3

            2. Clone the issue, remove the table content(changed format), copy the table from the original issue, and paste it to the cloned issue.

            Anusha Rutnam added a comment - From closed duplicate JRACLOUD-81028 – Number list in the table description changes the format while cloning the issue Issue Summary Cloning is changing the table format if the table description has a numbering list. Steps to Reproduce 1. Create an issue(I tried  task  issue type). 2. Create a table in the  description  and use the following in one of the columns. 1. test1 2. test2 3. test3 3. Clone the issue. Attaching the Screen Recording. Expected Results The table is cloned as it is. Actual Results The table format changes in the cloned issue. Workaround There are a couple of workarounds. 1. Try the following format 1 - test1 2 - test2 3 - test3 2. Clone the issue, remove the table content(changed format), copy the table from the original issue, and paste it to the cloned issue.

              jchen2@atlassian.com Jimmy
              ec42d141de9c Marcelo B
              Affected customers:
              4 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: