-
Suggestion
-
Resolution: Answered
-
None
-
None
-
None
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
JIRA Service Desk is the outcome of JIRA ViewPort aka Alternative JIRA Views ( JRA-27613 ).
After JRA-1330 ( field level security permission) was closed with "Won't fix", we all had high hopes because JRA-27613 was the long missing answer to achieve the same goals without having JRA-1330.
Please fulfill the expectations and promises you made and turn JIRA Service Desk
- into a dedicated application (e.g. own URL and instance) to serve as an external customer-facing support system interacting with JIRA
- and therefore adjust the licensing accordingly
- derived from
-
JRASERVER-1330 Provide field-level security permissions
- Closed
-
JRASERVER-27613 Alternative JIRA Views
- Closed
- incorporates
-
JSDSERVER-62 Add Permission so user can only view Portal and not JIRA.
- Closed
-
JSDSERVER-85 Allow license sits for customers
- Closed
- relates to
-
JSDCLOUD-201 Enhance JIRA Service Desk to run as external customer-facing support system as promised in JRA-27613
- Closed
- links to
[JSDSERVER-201] Enhance JIRA Service Desk to run as external customer-facing support system as promised in JRA-27613
Workflow | Original: JAC Suggestion Workflow [ 3011224 ] | New: JAC Suggestion Workflow 3 [ 3648642 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2663800 ] | New: JAC Suggestion Workflow [ 3011224 ] |
Workflow | Original: JSD Suggestion Workflow - TEMP [ 2322230 ] | New: Confluence Workflow - Public Facing v4 [ 2663800 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Workflow | Original: JSD Suggestion Workflow [ 2052645 ] | New: JSD Suggestion Workflow - TEMP [ 2322230 ] |
Workflow | Original: JSD Suggestion Workflow - TEMP [ 2048511 ] | New: JSD Suggestion Workflow [ 2052645 ] |
Workflow | Original: JSD Suggestion Workflow [ 1279627 ] | New: JSD Suggestion Workflow - TEMP [ 2048511 ] |
Description |
Original:
JIRA Service Desk is the outcome of JIRA ViewPort aka Alternative JIRA Views ( After Please fulfill the expectations and promises you made and turn JIRA Service Desk - into a dedicated application (e.g. own URL and instance) to serve as an external customer-facing support system interacting with JIRA - and therefore adjust the licensing accordingly |
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-201]. {panel} JIRA Service Desk is the outcome of JIRA ViewPort aka Alternative JIRA Views ( After Please fulfill the expectations and promises you made and turn JIRA Service Desk - into a dedicated application (e.g. own URL and instance) to serve as an external customer-facing support system interacting with JIRA - and therefore adjust the licensing accordingly |
Link |
New:
This issue relates to |
Workflow | Original: TTT: Simple Issue Tracking Workflow [ 588632 ] | New: JSD Suggestion Workflow [ 1279627 ] |
Status | Original: Done [ 10044 ] | New: Closed [ 6 ] |
how is this marked as done? I was about to roll JIRA (and service desk) out in our network but this is a show stopper. I see a ton of people have requested this and there is no way my organisation is going to purchase JIRA twice in order to run a public facing solution! Why isn't it marketed as an INTERNAL service desk in your sales documentation!