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

Ability to export text fields with the resultant format instead of its markdown syntax

XMLWordPrintable

    • 2

    • 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.

      Summary

      Currently, exporting issues to CSV/HTML will result in text fields displaying the value before the Markdown conversion.

      See the example below:

      That might make it hard for users to read the data when building reports.

      Suggestion

      Provide the ability to have the have the data exported as displayed after the markdown conversion instead of exporting the text in raw markdown syntax.

        1. Screen Shot 2021-02-16 at 14.34.58.png
          Screen Shot 2021-02-16 at 14.34.58.png
          33 kB
        2. Screen Shot 2021-02-16 at 14.35.48.png
          Screen Shot 2021-02-16 at 14.35.48.png
          79 kB

          Form Name

            [JRACLOUD-76037] Ability to export text fields with the resultant format instead of its markdown syntax

            Tair Tidhar made changes -
            Component/s Original: Jira Issue Search - Frontend [ 53297 ]
            Tair Tidhar made changes -
            Component/s New: Issue - Search - Frontend only [ 77950 ]
            Matthew Hunter made changes -
            Resolution New: Won't Fix [ 2 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]
            Matthew Hunter made changes -
            Labels Original: nin New: nin timeout-suggestion-bulk-close

            Matthew Hunter added a comment -
            Atlassian Update - March 2, 2024

            Hi everyone,

            Thank you for bringing this suggestion to our attention.

            As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team!

            Matthew Hunter added a comment - Atlassian Update - March 2, 2024 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new feature policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team!
            Yerbol Nisanbayev (Inactive) made changes -
            Assignee Original: Yerbol Nisanbayev [ 3947164d8b7f ] New: Jordan Koukides [ f9ef18c34e08 ]
            SET Analytics Bot made changes -
            Support reference count Original: 1 New: 2
            Tulsi made changes -
            Description Original: h3. Summary

            Currently, exporting issues to CSV will result in text fields displaying the value before the Markdown conversion.

            See the example below:
             !Screen Shot 2021-02-16 at 14.34.58.png|thumbnail! !Screen Shot 2021-02-16 at 14.35.48.png|thumbnail!

            That might make it hard for users to read the data when building reports.

            h3. Suggestion

            Provide the ability to have the have the data exported as displayed after the markdown conversion instead of exporting the text in raw markdown syntax.             		New: h3. Summary

            Currently, exporting issues to CSV/HTML will result in text fields displaying the value before the Markdown conversion.

            See the example below:
             !Screen Shot 2021-02-16 at 14.34.58.png|thumbnail! !Screen Shot 2021-02-16 at 14.35.48.png|thumbnail!

            That might make it hard for users to read the data when building reports.

            h3. Suggestion

            Provide the ability to have the have the data exported as displayed after the markdown conversion instead of exporting the text in raw markdown syntax.
            SET Analytics Bot made changes -
            Support reference count New: 1
            Yerbol Nisanbayev (Inactive) made changes -
            Labels New: nin

              f9ef18c34e08 Jordan Koukides (Inactive)
              lalmeida@atlassian.com Leonardo De Almeida
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: