7fca56fba7c9 3a7162d9fd90 

I have used this method with ${reporter} and ${project}.  You might be able to use issuetype.  I do know you cannot use the requesttype.  

I used to default the summary and hide it to prevent users from changing the summary and losing the values in the subsequent field; however, Atlassian has since prevented Summary from being hidden as it is required.

3a7162d9fd90   I put that comment in 2.5 years ago!   I was able to recreate the steps though and it worked for me.  Here is what I did:

1. In an JSM Asset object (I called mine "Simple table") create an attribute with name 'SummaryAttribute' and of type  'Text'.   Populate a few objects where this attribute is 'Sum1', 'Sum2', 'Sum3'.    Have the 'Name' attribute be something else that you will recognize later in step 6
2. Create a custom field of type Assets with name 'SummaryAsObject' and make sure you add it to right screen that you intend to use for the Issue Type and Request Type
3. Configure the new Asset custom field like this:

 Filter scope (AQL): ObjectType = "Simple table"

Filter issue scope (AQL): SummaryAttribute = ${summary}

Allow search filtering by these attributes: Name, SummaryAttribute

Object attributes to display on issue view: SummaryAttribute, Name

4. Create a new Request Type with 2 fields.   First field is the normal Jira 'Summary' field and the second field being the new 'SummaryAsObject' custom field.   The order is important since the Filter issue scope (AQL) looks "above" I think

5. In the customer portal in the Summary field type in 'Sum2'

6. Click in the 'SummaryAsObject' field - the only option that should show up is what you configured in Step 1 for 'Sum2'

I did not try yet, but the same thing should work for ${reporter} - see link in another comment below, and this may also work for some other "issue" (non custom) fields.

7fca56fba7c9

You mentioned you were able to use the summary field as place holder in the portal? 

https://jira.atlassian.com/browse/JSDCLOUD-10989?focusedId=3076607&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-3076607

Can you share how you could to it? I tried in many many ways, no lucky so far

Happy New Year, everyone! May it be filled with joy, success, and - who knows - maybe even some miracles. Like Atlassian resolving to fix this bug. We can dream, right?

Having an option to refference Request Types in Issue Scope would be life-saving. Using separate fields per request type looks just unprofessional. I have tried with dummy object corresponding to each issue type... but it's not possible to hide Assets fields on Portal. That doesn't seem to be a difficult change, but at the same time it will make Assets extremely usefull.

Fingers crossed, Atlassian!

Any news on the progress of this one?
BR Toby

Merry Christmas to everyone and I wish us all that Atlassian has many New Year's resolutions - e.g. to solve this issue!

This is a major issue for us.  We need to have this addressed and fixed sooner than later.

We found these two articles helpful (maybe this is a working workaround fo r you):

• https://confluence.atlassian.com/jirakb/filter-insight-objects-within-a-issue-based-on-other-insight-field-storing-multiple-objects-1142453352.html
• https://jira.atlassian.com/browse/JSDCLOUD-9927

Our filter that references another custom field works well.

// Filter issue scope (IQL): object HAVING outboundReferences(objecttype = "Service Offering" AND objectId IN (${customfield_10106${0}})) 

Anyone find any workarounds for this?  In particular I have been trying to have the exact example in the Description above.  

The only things I could get to work (in Jira Cloud) is the Summary field and a User reference with the Reporter field. 

Somebody from the Atlassian team just gave this example - but does not seem to work either (Jira Cloud)

object HAVING outR(objectType=userAD AND object HAVING inR(Key=${customfield_XXXXX}))