-
Bug
-
Resolution: Answered
-
Medium
NOTE: This bug report is for JIRA Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding bug report.
It seems like a regression from previous solved requests:
Steps to reproduce:
- Create a JIRA Service Desk
- Import issues from CSV or create issues using JIRA Create button into the Service Desk project.
- Set the reporter to be one of your Service Desk customers
Expected Behavior
The issue created/imported through JIRA would be displayed under "My Requests" in the customer portal.
Actual Behavior
The issue is only visible through JIRA.
The Service Desk customer do not have access.
Also, any communication in the issues created/import via JIRA do not trigger an email notification to the involved people.
- has a derivative of
-
JSDCLOUD-1754 As a JIRA User, I'd like to set the Request Type while Creating an Issue
- Closed
- is a regression of
-
JSDCLOUD-55 Issues created before Service Desk will not show in the user's portal
- Closed
- is related to
-
JSDSERVER-1445 Issues created using JIRA create button, or CSV import, do not appear under "My Requests" of JIRA Service Desk. Also, the email communication does not work for those issues.
-
- Closed
-
[JSDCLOUD-1445] Issues created using JIRA create button, or CSV import, do not appear under "My Requests" of JIRA Service Desk. Also, the email communication does not work for those issues.
Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2303712 ] | New: JAC Bug Workflow v3 [ 3443567 ] |
Status | Original: Done [ 10044 ] | New: Closed [ 6 ] |
Workflow | Original: JSD Bug Workflow v5 [ 2057659 ] | New: JSD Bug Workflow v5 - TEMP [ 2303712 ] |
Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2055069 ] | New: JSD Bug Workflow v5 [ 2057659 ] |
Workflow | Original: JSD Bug Workflow v5 [ 1954674 ] | New: JSD Bug Workflow v5 - TEMP [ 2055069 ] |
Workflow | Original: JSD Bug Workflow v4 [ 1874455 ] | New: JSD Bug Workflow v5 [ 1954674 ] |
Description |
Original:
It seems like a regression from previous solved requests: * https://jira.atlassian.com/browse/JSD-830 * https://jira.atlassian.com/browse/JSD-55 *Steps to reproduce:* # Create a JIRA Service Desk # Import issues from CSV or create issues using JIRA Create button into the Service Desk project. # Set the reporter to be one of your Service Desk customers *Expected Behavior* The issue created/imported through JIRA would be displayed under "My Requests" in the customer portal. *Actual Behavior* The issue is only visible through JIRA. The Service Desk customer do not have access. Also, any communication in the issues created/import via JIRA do not trigger an email notification to the involved people. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This bug report is for *JIRA Service Desk Cloud*. Using *JIRA Service Desk Server*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDSERVER-1445]. {panel} It seems like a regression from previous solved requests: * https://jira.atlassian.com/browse/JSD-830 * https://jira.atlassian.com/browse/JSD-55 *Steps to reproduce:* # Create a JIRA Service Desk # Import issues from CSV or create issues using JIRA Create button into the Service Desk project. # Set the reporter to be one of your Service Desk customers *Expected Behavior* The issue created/imported through JIRA would be displayed under "My Requests" in the customer portal. *Actual Behavior* The issue is only visible through JIRA. The Service Desk customer do not have access. Also, any communication in the issues created/import via JIRA do not trigger an email notification to the involved people. |
Link |
New:
This issue is related to |
Project Import | New: Sun Apr 02 00:24:18 UTC 2017 [ 1491092658763 ] |
Labels | New: affects-cloud affects-server |
Workflow | Original: JSD Bug Workflow v2 [ 1603219 ] | New: JSD Bug Workflow v4 [ 1616022 ] |