-
Suggestion
-
Resolution: Duplicate
-
None
-
None
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
We are in process of evaluating JIRA Service Desk solution setup within our Company. We tested JSD 1.2 – 2.3 features. We have major blocking Issue for our setup JIRA + JIRA Service Desk.
First, let me explain our business case Issue. We are using one JIRA project for supporting many different customers. Customer information is present as custom field data. Our plan would be having for each customer their own Request Type forms.
Must have:
- one Customer Portal with many Individual Customer Request Types (Forms),
- each customer should not have permission to access Request Forms but only their own
This requires:
- Additional Permission Scheme with Request Type Access level,
- Or we can define per user access mapping restriction to each Request Type
We can’t implement many projects = Customer Portals as it is current setup.
Is it possible to add this suggestion as new feature?
- duplicates
-
JSDSERVER-195 Ability to restrict ticket creation for certain "Request Types"
- Closed
- relates to
-
JSDCLOUD-1634 One Customer Portal with Permission Scheme for Request Type Access (Forms) level
- Closed
- mentioned in
-
Page Failed to load
[JSDSERVER-1634] One Customer Portal with Permission Scheme for Request Type Access (Forms) level
Remote Link | New: This issue links to "Page (Confluence)" [ 771169 ] |
Workflow | Original: JAC Suggestion Workflow [ 3011860 ] | New: JAC Suggestion Workflow 3 [ 3649457 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2665329 ] | New: JAC Suggestion Workflow [ 3011860 ] |
Workflow | Original: JSD Suggestion Workflow - TEMP [ 2325709 ] | New: Confluence Workflow - Public Facing v4 [ 2665329 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Workflow | Original: JSD Suggestion Workflow [ 2053619 ] | New: JSD Suggestion Workflow - TEMP [ 2325709 ] |
Workflow | Original: JSD Suggestion Workflow - TEMP [ 2048771 ] | New: JSD Suggestion Workflow [ 2053619 ] |
Workflow | Original: JSD Suggestion Workflow [ 1280570 ] | New: JSD Suggestion Workflow - TEMP [ 2048771 ] |
Description |
Original:
We are in process of evaluating JIRA Service Desk solution setup within our Company. We tested JSD 1.2 – 2.3 features. We have major blocking Issue for our setup JIRA + JIRA Service Desk.
First, let me explain our business case Issue. We are using one JIRA project for supporting many different customers. Customer information is present as custom field data. Our plan would be having for each customer their own Request Type forms. Must have: - one Customer Portal with many Individual Customer Request Types (Forms), - each customer should not have permission to access Request Forms but only their own This requires: - Additional Permission Scheme with Request Type Access level, - Or we can define per user access mapping restriction to each Request Type We can’t implement many projects = Customer Portals as it is current setup. Is it possible to add this suggestion as new feature? |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-1634]. {panel} We are in process of evaluating JIRA Service Desk solution setup within our Company. We tested JSD 1.2 – 2.3 features. We have major blocking Issue for our setup JIRA + JIRA Service Desk. First, let me explain our business case Issue. We are using one JIRA project for supporting many different customers. Customer information is present as custom field data. Our plan would be having for each customer their own Request Type forms. Must have: - one Customer Portal with many Individual Customer Request Types (Forms), - each customer should not have permission to access Request Forms but only their own This requires: - Additional Permission Scheme with Request Type Access level, - Or we can define per user access mapping restriction to each Request Type We can’t implement many projects = Customer Portals as it is current setup. Is it possible to add this suggestion as new feature? |
Link |
New:
This issue relates to |
Component/s | New: Licensing & Permissions [ 44395 ] | |
Component/s | Original: Project Permissions [ 37590 ] |