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.

      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.

          Form Name

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

            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. 

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

            Sven.H added a comment -

            We have the same problem with JIRA 6.4.12 and JIRA Agile 6.7.11

            Sven.H added a comment - We have the same problem with JIRA 6.4.12 and JIRA Agile 6.7.11

            Hi infrastruktur2,

            I have moved this issue to the JIRA Agile project so that the the JIRA Agile developers can triage it accordingly. In the meanwhile, I will reset the issue's priority to "Minor" until it gets triaged by them.

            Regards,

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

            Oswaldo Hernandez (Inactive) added a comment - Hi infrastruktur2 , I have moved this issue to the JIRA Agile project so that the the JIRA Agile developers can triage it accordingly. In the meanwhile, I will reset the issue's priority to "Minor" until it gets triaged by them. Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            Hello,

            why this bug is a non-critical? Work with different language is a native feature especially in high-priced applications. With this bug we can not migrate from a 25 user to 100 user license. when will this bug fixed?

            Kind Regards

            Alex

            sidion GmbH added a comment - Hello, why this bug is a non-critical? Work with different language is a native feature especially in high-priced applications. With this bug we can not migrate from a 25 user to 100 user license. when will this bug fixed? Kind Regards Alex

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

                Created:
                Updated:
                Resolved: