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

Allow CSV Import for Request Participants field

XMLWordPrintable

    • 2
    • 21

    • 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.

      Problem Definition

      Unable to import Request Participants field using CSV import feature. For both user-facing CSV import and admin-facing CSV import features.

      Suggested Solution

      Allow Request Participants to be included in CSV import

      Why this is important

      • To correctly export/import via CSV (currently CSV export includes Request participant)
      • To automate the assignment of Request Participant via CSV create issue or update issue

      Workaround

      Using REST API to add Request participant

            [JSDCLOUD-7799] Allow CSV Import for Request Participants field

            Bettina Lippisch added a comment -

            This is needed urgently. This is available in Server and it will disrupt operations. This is unfortunately that we are made to move from Server to Cloud when the Cloud version is lacking critical features like this to have a seamless migration. The workaround will not work for our operations team, unfortunately. 

            Bettina Lippisch added a comment - This is needed urgently. This is available in Server and it will disrupt operations. This is unfortunately that we are made to move from Server to Cloud when the Cloud version is lacking critical features like this to have a seamless migration. The workaround will not work for our operations team, unfortunately. 

            Mike DiGiantomasso added a comment -

            i see now.   you have to specifiy a separate column for each participant.   but most problematic, you cannot use  portal-only user email address and allow Jira to translate.  you have to use the actual ID.  this worked

             

            qm:d16253b6-700a-4bf7-8f22-4b239ea1ac6c:5ba14354fcec6728d7c0d1cd

            Mike DiGiantomasso added a comment - i see now.    you have to specifiy a separate column for each participant.   but most problematic, you cannot use  portal-only user email address and allow Jira to translate.  you have to use the actual ID.  this worked   qm:d16253b6-700a-4bf7-8f22-4b239ea1ac6c:5ba14354fcec6728d7c0d1cd

            Mike DiGiantomasso added a comment -

            this now works for internal users.   However i need it to work by passing in a portal only user email address and having that stay populated

            Mike DiGiantomasso added a comment - this now works for internal users.   However i need it to work by passing in a portal only user email address and having that stay populated

            Mike DiGiantomasso added a comment -

            Odd, there is no error after the import either.  just leaves it null

            Mike DiGiantomasso added a comment - Odd, there is no error after the import either.  just leaves it null

              Unassigned Unassigned
              rbaldasso@atlassian.com Rodrigo Baldasso (Inactive)
              Votes:
              34 Vote for this issue
              Watchers:
              21 Start watching this issue

                Created:
                Updated: