-
Suggestion
-
Resolution: Unresolved
-
None
-
242
-
29
-
NOTE: This suggestion is for Jira Service Management Data Center. Using Jira Service Management Cloud? See the corresponding suggestion.
Problem Definition
Currently, Assignee field is hidden from the portal.
Suggested Solution
Allow to set Assignee field to be visible by the customers in read-only mode
Why this is important
In some cases, we would like to make the Assignee to be visible. Example:
- Show Assignee field on "Account Access" requests, so the internal users know who is the user to follow up with if the request hasn't been updated.
Workaround
As a part of Jira Service Management Data Center 4.21 we have released column configuration on the Help center’s request list view. This allows Jira admins to select the columns that they would like to appear in their customer's requests list. It also allows customers to configure and order the columns.
The available fields are type, reference, summary, status, service project, requester, created date, updated date, due date, assignee and priority.
Please refer to our documentation to learn how to configure the requests list.
While assignee can now be viewed in the request list view, it cannot be viewed in an individual request, so we will keep this suggestion open for now.
Client would like a way to add assignee as a VISIBLE field and not just a hidden field on customer view.
- has a derivative of
-
JSDSERVER-1900 Customers not able to see Assignee of issues on Portal view of My Tickets
- Closed
- is duplicated by
-
JSDSERVER-1900 Customers not able to see Assignee of issues on Portal view of My Tickets
- Closed
- is related to
-
JSDSERVER-4580 Change columns in Customer Portal 'requests' page
- Closed
-
JSDSERVER-4328 Add fields (view only) in Customer Portal
- Future Consideration
- relates to
-
JSDCLOUD-328 Allow Assignee to be Shown on Customer Portal
- Reviewing
- blocks
-
PSSRV-15896 Loading...
- links to
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...