-
Suggestion
-
Resolution: Low Engagement
-
None
-
None
-
None
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
We are using JIRA, JIRA Servicedesk and Confluence, with Confluence also serving as a knowlegde base for our customers at the Servicedesk.
In Confluence it is possible to use JIRA links, powerful and useful! However, if one uses such a link in a Confluence space accessible to customers (who can only access the Servicedesk Portal) the JIRA links are dead to them. This is not well understood by our customers and does limit the combined power of Confluence and JIRA Servicedesk greatly.
What would make the combination of JIRA Servicedesk and Confluence much more powerfull would be an extra authentication step with JIRA links in Confluence;
- if a person has user-access to JIRA, wave through
- if a person has SD-customer-portal acces, send through to the customer portal view
- If a person has no JIRA access, show notification 'you are not authorised'
If this would become possible, we could use the JIRA-macro's in Confluence for a great many more purposes;
- Release notes
- Customer specific reports
- Interactive link in Questions (e.g. the following ticket has been created based on this discussion)
- ... etc.
"Workaround" is to include the SD-portal link in Confluence, but this is a) no JIRA-link and b) not interactive
- relates to
-
JSDCLOUD-4260 Confluence + JIRA Servicedesk > Linked JIRA issues are dead to Servicedesk Portal customers
- Closed
[JSDSERVER-4260] Confluence + JIRA Servicedesk > Linked JIRA issues are dead to Servicedesk Portal customers
Resolution | Original: Won't Do [ 10000 ] | New: Low Engagement [ 10300 ] |
Status | Original: Closed [ 6 ] | New: Closed [ 6 ] |
Resolution | New: Won't Do [ 10000 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
Workflow | Original: JAC Suggestion Workflow [ 3011742 ] | New: JAC Suggestion Workflow 3 [ 3649301 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2665933 ] | New: JAC Suggestion Workflow [ 3011742 ] |
Workflow | Original: JSD Suggestion Workflow - TEMP [ 2324052 ] | New: Confluence Workflow - Public Facing v4 [ 2665933 ] |
Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
Workflow | Original: JSD Suggestion Workflow [ 2052575 ] | New: JSD Suggestion Workflow - TEMP [ 2324052 ] |
Workflow | Original: JSD Suggestion Workflow - TEMP [ 2048096 ] | New: JSD Suggestion Workflow [ 2052575 ] |
Workflow | Original: JSD Suggestion Workflow [ 1596095 ] | New: JSD Suggestion Workflow - TEMP [ 2048096 ] |
Hi,
Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.
This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers).
We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.
To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.
Regards,
Jira Service Management, Server & Data Center