Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-82250

Importing issues with External System Import (JSON) doesn't set Security level

XMLWordPrintable

      Issue Summary

      When importing issues via External System Import with JSON format Jira does not set the Security level.

      Steps to Reproduce

      1. Configure Security levels on project to have security level "Level 1" (don't set Default levels)
      2. Go to External System Import > JSON
      3. Adjust below Json to your project and use it for import:
      {  "projects": [
        {
            "key": "SAMPLE",
            "issues": [
                {
                    "externalId": "1",
                    "summary": "Test Security Level",
                    "issueType" : "[System] Service request",
                    "security": "Level 1"
                }
            ]
        }
    ]
}

      Expected Results

      Issue is created with Security Level set to "Level 1"

      Actual Results

      Issue is created without Security Level

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            [JRACLOUD-82250] Importing issues with External System Import (JSON) doesn't set Security level

            Matthew Hunter added a comment -
            Atlassian Update - November 19, 2024

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!
            Jira Cloud team

            Matthew Hunter added a comment - Atlassian Update - November 19, 2024 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team! Jira Cloud team

              Unassigned Unassigned
              207d30156835 Ivan Chapistrak
              Affected customers:
              1 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: