-
Suggestion
-
Resolution: Low Engagement
-
None
-
None
-
1
-
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
Problem Definition
Admin or agent face problem with attachment is not viewable from comment field and customer can't view it from Customer Portal . It is due to comment field renderer is set to Default Text Renderer instead Wiki Style Renderer. This problem is not noticeable by admin , because the setting was used by others project . JIRA Service Desk just reused the Default Field Configurations.
Suggested Solution
Admin get notified when create new Service Desk project . Comment field renderer should configured as Wiki Style Renderer , if not customer won't able to view attachment from Customer Portal
- is related to
-
JSDCLOUD-5306 JIRA Service desk customer portal does not show attachements
-
- Closed
-
-
JSDSERVER-2378 Attachments uploaded by JIRA Service Desk Customer end up in the secure attachment directory
-
- Closed
-
- relates to
-
CLOUD-10641 Comment field with " Default Text Renderer " still showing " Wiki Style Renderer " options
-
- Closed
-
-
JRACLOUD-82048 Ability to set [default text renderer] for comments field in field config is misleading
-
- Gathering Impact
-
-
JSDSERVER-3344 Comment field with " Default Text Renderer " still showing " Wiki Style Renderer " options
-
- Gathering Impact
-
-
JSDCLOUD-3137 As admin, would like to get notified when new project created using default field configuration with comment renderer set to 'Default Text Renderer'
- Closed
-
JSDSERVER-1042 Service Desk Text Field Renderer should not inherit Default Field Configuration
- Closed
-
JSDSERVER-4957 Customer portal should always use wiki style renderer
- Gathering Interest
-
JSDS-569 Loading...
- was cloned as
-
DESK-4561 Loading...
Form Name |
---|
[JSDSERVER-3137] As admin, would like to get notified when new project created using default field configuration with comment renderer set to 'Default Text Renderer'
Link | New: This issue relates to CLOUD-11679 [ CLOUD-11679 ] |
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 [ 3012068 ] | New: JAC Suggestion Workflow 3 [ 3649588 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2663989 ] | New: JAC Suggestion Workflow [ 3012068 ] |
Link |
New:
This issue relates to |
Support reference count | New: 1 |
Workflow | Original: JSD Suggestion Workflow - TEMP [ 2322951 ] | New: Confluence Workflow - Public Facing v4 [ 2663989 ] |
Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
Workflow | Original: JSD Suggestion Workflow [ 2052747 ] | New: JSD Suggestion Workflow - TEMP [ 2322951 ] |
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