• Type: Bug
• Resolution: Timed out
• Priority: Low
• Component/s: Request Participants
• Labels:

  • timeout-bulk-close202012

1. 

   image-2019-10-15-10-50-50-270.png

   58 kB

   14/Oct/2019 11:50 PM

2. 

   screenshot-1.png

   1.79 MB

   31/Oct/2019 12:04 AM

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

Nicole made changes - 21/Dec/2020 9:50 PM

Resolution		New: Timed out [ 10 ]
Status	Original: Gathering Impact [ 12072 ]	New: Closed [ 6 ]

Nicole made changes - 21/Dec/2020 9:50 PM

Labels

New: timeout-bulk-close202012

Bugfix Automation Bot made changes - 23/Dec/2019 6:00 PM

Support reference count

Original: 1

New: 2

Eduardo Santos made changes - 23/Dec/2019 12:56 PM

Description

Original: h3. 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. h3. Environment Cloud h3. Steps to Reproduce  # Add user as request participant. (Make sure the email visibility is open to anyone) # Perform CSV export h3. Expected Results "Request Participant" field comes with *Account ID* format. h3. Actual Results "Request Participant" field comes with *name (email address)*. h3. Notes Due to this, admin can't use the same file to import. Admin must edit the field. h3. Workaround  Currently there is no known workaround for this behavior. A workaround will be added here when available

New: h3. 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. h3. Environment Cloud h3. Steps to Reproduce  # Add user as request participant. (Make sure the email visibility is open to anyone) # Perform CSV export h3. Expected Results "Request Participant" field comes with *Account ID* format. h3. Actual Results "Request Participant" field comes with *name (email address)*. h3. Notes Due to this, admin can't use the same file to import. Admin must edit the field. h3. Workaround Create a ticket with support at [here|https://support.atlassian.com/contact/#/] asking for the CSV with email address and accountIDs

Andrea made changes - 31/Oct/2019 12:04 AM

Attachment

New: screenshot-1.png [ 379767 ]

Radu made changes - 15/Oct/2019 1:38 AM

Status

Original: Needs Triage [ 10030 ]

New: Gathering Impact [ 12072 ]

Agus made changes - 14/Oct/2019 11:50 PM

Attachment

New: image-2019-10-15-10-50-50-270.png [ 378260 ]

Atiqah Roslan made changes - 11/Oct/2019 7:50 AM

Description

Original: h3. 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. h3. Environment Cloud h3. Steps to Reproduce  # Add user as request participant. (Make sure the email visibility is open to anyone) # Perform CSV export h3. Expected Results "Request Participant" field comes with *email address or Account ID* format. h3. Actual Results "Request Participant" field comes with *name (email address)*. h3. Notes Due to this, admin can't use the same file to import. Admin must edit the field. h3. Workaround  Currently there is no known workaround for this behavior. A workaround will be added here when available

New: h3. 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. h3. Environment Cloud h3. Steps to Reproduce  # Add user as request participant. (Make sure the email visibility is open to anyone) # Perform CSV export h3. Expected Results "Request Participant" field comes with *Account ID* format. h3. Actual Results "Request Participant" field comes with *name (email address)*. h3. Notes Due to this, admin can't use the same file to import. Admin must edit the field. h3. Workaround  Currently there is no known workaround for this behavior. A workaround will be added here when available

Ed Zhang (Automation) made changes - 08/Oct/2019 11:16 PM

Component/s		New: Request Participants [ 57690 ]
Component/s	Original: Project Administration - Issue type, fields and Other [ 53196 ]
Key	Original: JRACLOUD-73138	New: JSDCLOUD-8514
Project	Original: Jira Cloud (including JIRA Core) [ 18514 ]	New: Jira Service Desk Cloud [ 18512 ]

Bugfix Automation Bot made changes - 08/Oct/2019 6:00 PM

Support reference count

New: 1

Atiqah Roslan created issue - 08/Oct/2019 2:27 PM