Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-10106

Cannot do Project Import between different language that have JIRA Agile values.

XMLWordPrintable

      Steps to Reproduce:

      1. Install 2 new JIRA Instance with latest Agile on different language.
      2. Create a new Scrum Board with its project.
      3. Create stories and assigned into an epic.
      4. Insert value on the Story Point field.
      5. Do an XML Backup and do the import in the other JIRA Instance with different language.

      Expected Results:

      The project import will be successful, the JIRA Agile custom field and Issue types will be automatically translated into the target Instance language.

      Actual Results:

      The project import cannot be done, because the JIRA Agile custom fields and Issue Types are still in English.

      Associated Information:

      Notes:

      • After unlocking the custom field using above KB and trasnlate it, the project import is still reject it.
      • Changing the JIRA Instance default language still makes the custom field name not changing, including the Issue Types.

        1. After Translation.png
          After Translation.png
          69 kB
        2. Project Import - Epic not changed.png
          Project Import - Epic not changed.png
          56 kB
        3. Project Import - Epic to Epos.png
          Project Import - Epic to Epos.png
          70 kB

            [JSWSERVER-10106] Cannot do Project Import between different language that have JIRA Agile values.

            Bugfix Automation Bot made changes -
            Minimum Version New: 6.01
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2851973 ] New: JAC Bug Workflow v3 [ 2936965 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545895 ] New: JAC Bug Workflow v2 [ 2851973 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1550978 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545895 ]

            Gaven Ray added a comment -

            The problem still exists in JIRA 7.3.6. You need to fix the project importer to not see that they are different fields. 

            Gaven Ray added a comment - The problem still exists in JIRA 7.3.6. You need to fix the project importer to not see that they are different fields. 
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: fixme New: affects-server fixme
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 909810 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1550978 ]

            Oswaldo Hernandez (Inactive) added a comment -

            Hi all,

            This is the same as JRA-35937.

            Consequently, I have resolved this issue in favour of JRA-35937, please watch that issue instead for further updates.

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - Hi all, This is the same as JRA-35937 . Consequently, I have resolved this issue in favour of JRA-35937 , please watch that issue instead for further updates. Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .
            Oswaldo Hernandez (Inactive) made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]
            Oswaldo Hernandez (Inactive) made changes -
            Link New: This issue duplicates JRA-35937 [ JRA-35937 ]

              Unassigned Unassigned
              jrahmadiputra Julian (Inactive)
              Affected customers:
              4 This affects my team
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: