-
Bug
-
Resolution: Won't Fix
-
Low
-
None
-
2.2, 2.3.2
Steps to Reproduce:
- Create two dummy Service Desk project.
- Login as Customer and access one of the Customer Portal.
- Create a new Request.
- Log out and logging in as JIRA Admin with Agents permission.
- Move the issue that is just recently created to the second dummy SDS project without making any changes on any fields.
Expected Result:
- With the same Issue Type and Request Type, the issue moved without any details missing.
Actual Result:
- In Service Desk request section, the Request Type is "No Match"
Notes:
- The issue is moved without any issue and it is showing on the customer "My Request" page.
- Including Customer Request Type in the View Issue screen will shown the correct Request Type.
- relates to
-
JSDSERVER-3613 Allow For Selecting Customer Request Types When Moving Issues Between SD Projects
- Closed
Form Name |
---|
[JSDSERVER-1633] Request Type value is "No Match" when being moved.
Comment | [ A comment with security level 'atlassian-staff' was removed. ] |
Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2304155 ] | New: JAC Bug Workflow v3 [ 3125216 ] |
Status | Original: Done [ 10044 ] | New: Closed [ 6 ] |
Workflow | Original: JSD Bug Workflow v5 [ 2058124 ] | New: JSD Bug Workflow v5 - TEMP [ 2304155 ] |
Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2055653 ] | New: JSD Bug Workflow v5 [ 2058124 ] |
Workflow | Original: JSD Bug Workflow v5 [ 1955674 ] | New: JSD Bug Workflow v5 - TEMP [ 2055653 ] |
Workflow | Original: JSD Bug Workflow v4 [ 1615471 ] | New: JSD Bug Workflow v5 [ 1955674 ] |
Labels | Original: mfd | New: affects-server mfd |
Workflow | Original: JSD Bug Workflow v2 [ 1602473 ] | New: JSD Bug Workflow v4 [ 1615471 ] |
Workflow | Original: JSD Bug Workflow [ 1398583 ] | New: JSD Bug Workflow v2 [ 1602473 ] |
Workflow | Original: TTT: Simple Issue Tracking Workflow [ 840376 ] | New: JSD Bug Workflow [ 1398583 ] |