-
Suggestion
-
Resolution: Unresolved
-
518
-
-
Issue Summary
At the moment the only custom fields that can be used as placeholders are Assets custom fields and this feature would extend support for standard custom fields, like text fields
Steps to Reproduce
- In your Assets field configuration use an AQL that references a custom field that is not an Assets custom field, ie. SimpleTextCustomField - customfield_xxxxx
Expected Results
Your search results reflect the values in that custom field.
Actual Results
You don't get any results.
Workaround
Set up an Assets field that mimics the value of that custom field, ie. an SimpleTextCustomField Assets field, and set that Assets field as the placeholder and also set up an Automation rule that populates that Assets field when the relevant custom field is changed.
- is related to
-
- Gathering Interest
-
- Gathering Interest
-
ENT-2658 Failed to load
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
[JSDCLOUD-10185] Allow the use of other standard custom fields as placeholders in the filter issue scope AQL
Hi Team 👋,
First off, I want to apologise for the lack of updates on this feature request. We appreciate your engagement and understand how important this is to you.
As you might have seen on other forums, we’ve been making significant investments in upgrading our platform to improve reliability and performance. This work is critical to laying a strong foundation for future development and ensuring a smoother experience for all users.
Once these upgrades are fully released and stable, we’ll be in a much better position to revisit the roadmap and start addressing feature requests like this one.
We still absolutely want to address this issue and acknowledge the frustration it may be causing. Thank you for your patience and understanding as we work through these priorities. Your continued feedback is invaluable, and we’re committed to keeping you updated on our progress.
Thank you,
Mohamed Hassan | Product Manager, JSM Assets
It is unacceptable that we are facing technical limitations of the platform that have not been addressed since 2021 and prevent us from improving and simplifying the request form for users.
We should urgently have the "Organizations" field to filter objects in the ticket creation screen before the ticket is created!
=> Do you have any update, news or roadmap?
Merry Christmas to everyone and I wish us all that Atlassian has many New Year's resolutions - e.g. to solve this issue!
Having this work for more of the 'standard' fields like JSM 'Organizations' would be very beneficial step forward, since we can make much more flexible use of the JSM portal.
Also, please note that this has the most votes right now among the Suggestions for Assets component. So, it really should be under serious consideration for the implementation backlog. Question: is "Future Consideration" more or less closer than "Under Consideration" for the implementation backlog?
Hi,
Like i have share with Simran, the workaround is not applicable in my case : I have a user picker custom field (Recipient), and from the Recipient field, I use the Azure AD attribute plug in, which allows me to retrieve attributes from the AD from that field.
In this case, you can use the workaround.
That's why it's very important to have the possibility to add other custom field in AQL issuer Scope on a Asset field.
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?