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

Import Issues from CSV functionality doesn't allow the Assignee Field to be filled as unassigned

    XMLWordPrintable

Details

    • 4
    • 2
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      Problem Definition

      The Import Issues from CSV functionality accessed through the search issues page (see image below) won't allow the assignee field of the CSV to be filled as unassigned.

      For instance:
      summary, issueType, assignee
      summarytest, Bug, unassigned (won't work)
      summarytest2, Bug, (will work)

      Note: the CSV import functionality accessed through the admin page (see image below) allows it.

      Suggested Solution

      Allow the Import Issues from CSV functionality accessed through the search issues page to accept the assignee field as unassigned and reflect the behavior of the admin CSV import functionality.

      Why this is important

      Keep the consistency of functionalities behaviors. As we've checked that using the CSV importer from
      (admin only) external system import this same behavior works.

      Attachments

        1. screenshot-1.png
          screenshot-1.png
          13 kB
        2. screenshot-2.png
          screenshot-2.png
          51 kB

        Activity

          People

            Unassigned Unassigned
            dwoo@atlassian.com Daniel Woo
            Votes:
            9 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: