Pre-populate Fields from URL

[Steve Letch]

@Yatish Madhav 

Use a Scriptrunner Initialiser. There's templates in the adaptavist library.

[Steve Letch]

Will just add, if you want to help your users a bit, use a DB query to import your custom fields and their options into Assets, then you can put an Assets widget on a service desk KB page and people can then see the ID's of things.

[Yatish Madhav]

Thanks @Steve Letch -  that is assuming we have and pay for ScriptRunner for Jira right? We do not have that.

[Steve Letch]

@Yatish Madhav 

You could set a default value in the field but that would limit you to having that value set globally.

[jamesholcomb]

One important note, I had to all lowercase "customfield_" in the url query string to get this to work.

[Deleted user]

I created a web tool at https://booniepepper.gitlab.io/jira-former/

As of posting it can just do the basic summary and description filling (code heads: feel free to contribute or send me issues etc).

Does anyone know if there a way to make the description handle newlines well?

[Morten Junker Juul]

This works fine, but it does not work when using forms. And how would you have fields with conditions (show/hide from values selected in other fields) in a "Request type".  It would require a lot of request types if not using forms with field conditions.

Would really be nice if pre populate worked with forms also. 

[Jacob Jaskolka]

As others have mentioned, we need the ability to use Asset fields as the pre-filled value. The half-measures from Atlassian and then calling it a complete solution need to be addressed. 

Furthermore, as proforma forms are taking more of an active role, it should be available there too.

[Ashutosh Sharma]

For Forms, we have this open feature request: https://jira.atlassian.com/browse/JSDCLOUD-12177

[Josh Marsh]

Does anyone else run into the issue where if the customer is not already logged into the portal then the context part of the URL is overwritten when clicked/entered/selected? 
For example:
https://domain.atlassian.net/servicedesk/customer/portal/12/group/81/create/502?summary=This%20is%20my%20subject&customfield_12648=BCN-83
->
https://domain.atlassian.net/servicedesk/customer/portal/12/user/login?destination=portal%2F12%2Fgroup%2F81%2Fcreate%2F502

Crucially, is there a way to retain the field information in this scenario?

Thanks,
Josh

[Steven Cavanagh]

Yet another feature that JSM almost does.

[Asmatullah Latifi]

But its not working with Dropdown Feld ? any idea ? i tried like follow link:

https://ourdomainname.atlassian.net/servicedesk/customer/portal/19/group/63/create/312?customfield_13070=blocker

[Yatish Madhav]

Hey, I am looking to pre populate a JSM portal link with an @ user mention

Eg https://xxx.atlassian.net/helpcenter/it-service-management/portal/1031/group/1048/create/4372description=%5B~accountid%3A5cf51a2d22c5c3044e0ac3bd%5D+Please+provide+details+here&labels=testLabel&priority=1&summary=Assistance+needed

You will see that I added (in bold and urlencoded) a Jira user ID 5cf51a2d22c5c3044e0ac3bd - but it shows the below ...

Would like for it to pre populate into an @ user mention - something like this:

Please assist or shared with me another post that can help?

Thank you

[George Morgan]

In response to:  https://community.atlassian.com/forums/Jira-Service-Management-articles/Pre-populate-Fields-from-URL/bc-p/2315973#M2811

For cascading a single custom field with multiple cascading pickers, you can use a comma separated list of item ids for each of the drop downs.  You will need to know the ids for each of the selected items.  Example:

https://mydomain.atlassian.net/servicedesk/customer/portal/#/create/#?customfield_12345=2345,3456

where 2345 is the id associated with the first picker's value, and 3456 is the id of the value you want to select from the second picker.

I figured out what the correct IDs were by looking at the json for an existing request in the portal:  https://mydomain.atlassian.net/rest/servicedeskapi/request/REQ-ID

[Yatish Madhav]

Thanks all

@George Morgan unfortunately, that does not work - the below does (on Cloud and for me at least)

https://abc.atlassian.net/helpcenter/it-service-management/portal/123/group/456/create/789?customfield_12002=2345&customfield_12002%3A1=3456&description=Test+description

Where customfield_12002 is the custom field id, 2345 is the id of the 1st select value, 3456 is the id of the 2nd select value

I still wonder if it is is possible for user to pre-populate an @ mention of a user? Any idea anyone?

Thanks

Yatish

[George Morgan]

I guess the way it works on Cloud vs Data Center must be different.  I didn't build the form that I'm trying to populate so it also may have something to do with how the form was created.  Thanks for sharing how it worked for you in "Cloud".  I am using 10.3.16 data center.