Uploaded image for project: 'JIRA Importers Plugin'
  1. JIRA Importers Plugin
  2. JIM-1140

Support all Redmine customFields in Redmine 2.4 and 2.5

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • Icon: Low Low
    • redmine-2.1.0
    • redmine-2.0.5
    • Redmine
    • None

      Currently we only create Text and MultiChoice CustomFields from Redmine, because there was no way to know anything more about them via REST. Since Redmine 2.4 there is availiable REST endpoint which returns all definitions of Custom Fields - including their type / possible values etc.

      We should add support for new definitions of Custom Fields

            [JIM-1140] Support all Redmine customFields in Redmine 2.4 and 2.5

            Katherine Yabut made changes -
            Workflow Original: JIM - workflow v2 [ 1610869 ] New: JIM Suggestion Workflow v2 [ 3156413 ]
            Ignat (Inactive) made changes -
            Issue Type Original: Improvement [ 4 ] New: Suggestion [ 10000 ]
            Owen made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Closed [ 6 ] New: Closed [ 6 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIM Project Workflow (Software Simplified) [ 1607277 ] New: JIM - workflow v2 [ 1610869 ]
            Ignat (Inactive) made changes -
            Epic Link New: JIM-1146 [ 635086 ]
            Ignat (Inactive) created issue -

            Przemyslaw Borkowski (Inactive) added a comment -

            JIM now supports all custom fields that are allowed in issues.

            Known limitations:

            • JIM handles only Custom Fields that are created for issues - CFs created for projects/version/users etc will be ignored, as JIRA doesn't allow such fields
            • List field will be always created in JIRA as dropdown - Redmine allows to pick if it should be rendered as Dropdown or Checkboxes, unfortunately this information is not passed via REST, so we treat it always as a dropdown
            • Logic field - JIRA doesn't have boolean custom field, so it will be rendered as Radio buttons Custom Fields with two options: "Yes" and "No"

            Przemyslaw Borkowski (Inactive) added a comment - JIM now supports all custom fields that are allowed in issues. Known limitations: JIM handles only Custom Fields that are created for issues - CFs created for projects/version/users etc will be ignored, as JIRA doesn't allow such fields List field will be always created in JIRA as dropdown - Redmine allows to pick if it should be rendered as Dropdown or Checkboxes, unfortunately this information is not passed via REST, so we treat it always as a dropdown Logic field - JIRA doesn't have boolean custom field, so it will be rendered as Radio buttons Custom Fields with two options: "Yes" and "No"

            Przemyslaw Borkowski (Inactive) added a comment -

            This issue was requested by the customer under CAC comment: https://confluence.atlassian.com/display/JIRA/Importing+Data+from+Redmine?focusedCommentId=665421670#comment-665421670.

            Przemyslaw Borkowski (Inactive) added a comment - This issue was requested by the customer under CAC comment: https://confluence.atlassian.com/display/JIRA/Importing+Data+from+Redmine?focusedCommentId=665421670#comment-665421670 .

              Unassigned Unassigned
              Anonymous Anonymous
              Archiver:
              dnorton@atlassian.com Dave Norton

                Created:
                Updated:
                Resolved:
                Archived: