Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-64415

Redmine Importer does not allow mapping custom fields do those defined in JIRA, causing fields duplication

    • 2
    • 5
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Redmine importer duplicates custom fields every time an import is executed.
      Importer doesn't let you map custom fields to fields that are already defined in JIRA causing fields duplication.

            [JRASERVER-64415] Redmine Importer does not allow mapping custom fields do those defined in JIRA, causing fields duplication

            SET Analytics Bot made changes -
            UIS Original: 1 New: 2
            SET Analytics Bot made changes -
            UIS Original: 3 New: 1
            SET Analytics Bot made changes -
            UIS Original: 1 New: 3
            SET Analytics Bot made changes -
            UIS Original: 0 New: 1
            SET Analytics Bot made changes -
            UIS Original: 1 New: 0
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3062204 ] New: JAC Suggestion Workflow 3 [ 3690790 ]

            cc: ialexeyenko maybe this bug that takindele is describing is something that Jira bugfix team wants to look at. 

            Adam Jakubowski (Inactive) added a comment - cc: ialexeyenko maybe this bug that takindele is describing is something that Jira bugfix team wants to look at. 
            Owen made changes -
            Component/s Original: Backup & Restore - Import from Trac [ 44292 ]
            Owen made changes -
            Component/s New: Jira Importers Plugin [ 44190 ]
            Component/s Original: Backup & Restore - Import from Redmine [ 44290 ]

            takindele please read my comment here https://jira.atlassian.com/browse/JRASERVER-64415?focusedCommentId=966592&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-966592

            It is really hard to say if this is a bug. The behaviour is that when importer create new custom field it puts it into project context. 

            When you then import to another project you cannot select the previously created custom field as it is not visible to the next project.

            Workaround here is to manually change context of custom field to global after first import or create custom fields manually with global context before using any importer. 

            I don't think we should be messing with custom fields context from inside importer especially if the custom fields are created manually not by the importer itself.  

            Adam Jakubowski (Inactive) added a comment - takindele please read my comment here https://jira.atlassian.com/browse/JRASERVER-64415?focusedCommentId=966592&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-966592 It is really hard to say if this is a bug. The behaviour is that when importer create new custom field it puts it into project context.  When you then import to another project you cannot select the previously created custom field as it is not visible to the next project. Workaround here is to manually change context of custom field to global after first import or create custom fields manually with global context before using any importer.  I don't think we should be messing with custom fields context from inside importer especially if the custom fields are created manually not by the importer itself.  

              Unassigned Unassigned
              Anonymous Anonymous
              Votes:
              6 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: