-
Suggestion
-
Resolution: Fixed
-
240
-
1
-
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
Hi everyone,
Thank you for your interest in this issue.
We have shipped support for auto-populated request fields in Jira Service Management Data Center 4.22.
You can generate URLs that will automatically populate selected request fields with contextual data. This way you can direct your customers to the customer portal from an external website and transfer certain details into the request fields.
Learn how to set up URLS with auto-populated request fields.
Kind regards,
Charlie
Jira Service Management, Data Center & Server
I would like to integrate further into our JIRA Service desk and the idea of a pre-populated link to a specific request type would be ideal.
For example:
- User clicks on public link
- User redirected to request
- User notices that the summary and the description are already pre-popuated with contextual information
Implementation:
I suspect the most simple implementation would be URL parameters that pre-populate the summary/description.
Such as: https://<jira-base-url>/servicedesk/customer/portal/1/create/92?summary=Test&description=More%20Text%20for%20the%20description
The (better) alternative would be the ability to use headers but would be more complicated.
Use Case:
- Dynamically generated support links throughout applications (such as "Report a problem with this document" or "Request access to this page")
Thanks!
- is related to
-
- Closed
- relates to
-
- Closed
-
- Gathering Interest
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
[JSDSERVER-4049] Provide URL functionality for pre-populated summary/description
Can this also be applied to Business forms. url entry point like : https://<my_project>.atlassian.net/jira/core/projects/<project_name>/form/<form_name>/?summary=example
Hi everyone,
Thank you for your interest in this issue.
We have shipped support for auto-populated request fields in Jira Service Management Data Center 4.22.
You can generate URLs that will automatically populate selected request fields with contextual data. This way you can direct your customers to the customer portal from an external website and transfer certain details into the request fields.
Learn how to set up URLS with auto-populated request fields.
Kind regards,
Charlie
Jira Service Management, Data Center & Server
Adding to matthews comment: mpage
some minor additions, with ScriptRunnner
// --------------------------------------------------------------------- // Below made for dynamic url parem to fields fetch & populate def url2 = new URL(url) def queryParams = url2.query?.split('&') // safe operator for urls without query params def mapParams = queryParams.collectEntries { paramz -> paramz.split('=').collect { URLDecoder.decode(it) }} mapParams.each { k,v -> getFieldById(k).setFormValue(v); //Will give static type checking error, but works getFieldById(k).setReadOnly(true) // Some additional behaviours added getFieldById(k).setHelpText("Field has been attaempted to auto fill based on the request link") //setDescription //Currently implemented above setFormValue will work for text fields only //ToDo: Handle different field types, or atleast the ones required by project team } // ---------------------------------------------------------------------
The cloud behaviour that 26bde235439e describes was implemented in JSDCLOUD-133#comment-2364290 as a passion project of a former Atlassian employee, done in their spare time.
Sadly it's unlikely this will ever end up on Jira Server, at least not within the next 50 years, unless another wonderful employee passionately picks up the feature (or is bribed to pick up the feature).
Using Jira 8.13.6 with ServiceDesk 4.13.6 on-premise and the fields are not filled, very sad
@Manuel Lindner
We are using Cloud version of Atlassian Jira Service Desk. Not sure how to check the version number in this case.
cmarriott could you please give me the name of the class that parses URL parameters? I have an issue with my prod environment (5.3.1). It does not fill fields on Portal. I copied DB and installed 5.3.1 on test server and it works fine.
If I have a class name I will add it to log4j and find out why params are not parsed.
My prod is under nginx, however server logs show that params are passed through to Tomcat
127.0.0.1 888x118885x1 samhuawey [22/Jan/2025:14:48:25 +0300] "GET /servicedesk/customer/portal/9/create/469?summary=samtakoy
Update
Hm, I was able to resolve the issue on portal. For some reason I had two licenses: for JSM and Jira Core. I had no idea how it happened, product was installed 2 years ago by previous admin.
After I reapplied JSM license the Jira Core license was removed and URL parameters magically started to populate.