Uploaded image for project: 'Xporter for Jira'
  1. Xporter for Jira
  2. XPORTER-3811

Translated Insight Fields are not being exported by it's default name

    XporterXMLWordPrintable

Details

    • JIRAXPORTER 2021 Sprint 9, JIRAXPORTER 2021 Sprint 10

    • OK

    Description

      When you have an Insight Field that is translated, if you switch to the translated language, exporting by its default name is not working:

      Even if you use the default name and the ID the result will be the same.

      It should have the same behavior as with Jira Custom Fields.

      Attachments

        1. image-2021-07-03-09-02-49-933.png
          47 kB
          Tiago Silva [X]
        2. image-2021-07-03-09-03-13-344.png
          5 kB
          Tiago Silva [X]
        3. screenshot-2.png
          216 kB
          Luis Sousa

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. XPORTER-3873 Xporter is causing high CPU consumption when translating custom fields

          • Medium - Created by JIM during import process
          • Closed

          Activity

            People

              afro Andre Fernandes Rodrigues
              lpss Luis Sousa
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 3 days, 45 minutes
                  3d 45m