-
Suggestion
-
Resolution: Fixed
-
636
-
86
-
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
Hi all,
I’m pleased to let you know that support for the request type ‘Project’ and ‘Version’ fields will be added in the upcoming JSM 4.15 release. Support for the ‘Group’ field is still outstanding, however this is something we might consider for our roadmap in the future. Please see JSDSERVER-7097 to add further comments and votes related to the 'Group' field.
Charlie, JSM Server & Data Center Team
Please specify what fields you would like to see in the Customer Portal by adding comments to this issue.
Hi all,
Just to provide some update on this ticket. Currently JIRA Service Desk supports all custom fields except Group pickers, Project pickers and Version pickers. The Project one is not relevant to the portal's users – please let us know how you'd use it if it's relevant to you so that we can understand your use case. We haven't heard many customers asking for groups and versions and therefore they are not on our current roadmap. We'd like your use case for these ones, esp. the group field.
In terms of add-on fields from our partners, e.g. nFeed, this is something we would like to have in JSD in the future but are currently not on our short to medium term roadmap.
— JIRA Service Desk team
Hi everyone,
Thanks for your input! Reading the comments posted so far, these seem to be the common ones :
- Group picker
- Project picker
- Labels
- Multi level select
- Calculated number
Thanks for supporting JIRA Service Desk!
The JIRA Service Desk team
- is blocked by
-
JSDSERVER-1211 Customer Request Type not visible on edit and create screens
- Closed
-
DESK-4558 Failed to load
-
JSMDC-564 You do not have permission to view this issue
- is duplicated by
-
JSDSERVER-84 Implement existing custom fields in customer portal
-
- Closed
-
-
JSDSERVER-1243 custom field type - Project Picker could not be shown in the customer Portal
-
- Closed
-
-
JSDSERVER-243 Having the ability to add custom field or any fields in the customer portal form
- Closed
-
JSDSERVER-2433 Nfeed or similar for Jira On Demand
- Closed
- is related to
-
JSDSERVER-992 not able to use security levels for customers
-
- Closed
-
-
JSDSERVER-3154 Let custom fields be settled as mandatory on JIRA
-
- Closed
-
-
JSDSERVER-343 add new created Custom Field to all Request types in Customer Portal
- Closed
-
JSDSERVER-2240 Downloadable Attachment on the Request Form
- Closed
-
JSDSERVER-4433 Render URL Custom Fields as Links in Customer Portal
- Closed
-
JSDSERVER-100 As a Service Desk user, I'd like to be able to add custom field types to Service Desk
- Gathering Interest
-
JSDSERVER-173 Support custom field plugins in the Customer Portal
- Gathering Interest
-
JSDSERVER-787 third-party fields to ServiceDesk request types in the customer portal
- Gathering Interest
-
JSDSERVER-2961 Option to Display Time Tracking in Service Desk Customer Portal view for certain users
- Gathering Interest
-
JSDSERVER-3518 Add "Original Estimate" field to Customer Portal
- Gathering Interest
-
JSMDC-530 Loading...
- relates to
-
JSDSERVER-3587 Update "Setting up request types" documentation to list standard custom field types that cannot be shown in portal
- Closed
-
JSDCLOUD-86 Several picker field types can't be added to a request type
- Future Consideration
-
DESK-852 Loading...
-
DESK-1859 Loading...
-
DESK-1860 Loading...
-
DESK-1925 Loading...
-
DESK-2008 Loading...
- was cloned as
-
JSDSERVER-7097 'Group' custom field type can't be added to a request type
- Gathering Interest
- is cloned by
-
DESK-1582 Loading...
- 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...
-
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...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
Please also add support for Kepler Custom Fields PRO or provide functionality to pull external AD Users and Groups into custom fields....This would really help our use case and enable us to promote the adoption of service desk at an organization level...
We intended to use this custom field to help eliminate the need to verify information relating to a user account.
As an example, take a user that would like to modify their user account information. By providing a custom field connected directly with our AD the user can simply select the appropriate user to be modified. If there are 2 Lisa Smiths...they would select the correct Lisa Smith account.
In order to work around this limitation that we have just discovered, we will now simply present a text box for the user to enter their user account. This could result in getting the log in user name or the users full name and even spelling mistakes. This will now impact the service agent who will have to verify the exact AD account with the customer before sending the task to the implementing team. This is an extra step that would be unnecessary if we had the custom field.
We also wanted to dynamically pull in our department & branch listing's from AD which are centrally managed to be displayed and selected so we are not managing a separate listing of static information.
There were various other custom fields we wanted to create as well pulling from AD that we will now only be able to present a text box requiring service agent effort to validate prior to sending tasks to our implementing teams.
I hope that this can be addressed in the near future to support us rolling this out further...