Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-8514

When issue CSV import , the "Request Participant" field imported with wrong format

      Issue Summary

      Currently, in CSV issue export file , the "Request Participant" field exported as Name (email address) format. Admin can't use the same file to import the issue because it's only work with email address/account ID format.

      Environment

      Cloud

      Steps to Reproduce

      1. Add user as request participant. (Make sure the email visibility is open to anyone)
      2. Perform CSV export

      Expected Results

      "Request Participant" field comes with Account ID format.

      Actual Results

      "Request Participant" field comes with name (email address).

      Notes

      Due to this, admin can't use the same file to import. Admin must edit the field.

      Workaround

      Create a ticket with support at here asking for the CSV with email address and accountIDs

            [JSDCLOUD-8514] When issue CSV import , the "Request Participant" field imported with wrong format

            Nicole added a comment -
            Atlassian Update - December 21, 2020

            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 Service Management Cloud 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 via raising a ticket at https://support.atlassian.com.

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

            Nicole added a comment - Atlassian Update - December 21, 2020 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 Service Management Cloud 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 via raising a ticket at https://support.atlassian.com . Thank you again for providing valuable feedback to our team! Jira Service Management Cloud team

              Unassigned Unassigned
              nroslan Atiqah Roslan
              Affected customers:
              1 This affects my team
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: