Have you considered this further?  We use Assets for our Service Items and used to hide them on the customer form because users don't always select the correct one.  Now, even with prompting they still don't always pick the right one.  We really need to hide it with default information in there.

Hi again Atlassian. 

Like others before me here I am requesting an update on the progress of this ticket. I see the issue has Status Future consideration. In the description of the status it clearly states that the ticket will be re-evaluated within a year. 

Status Future Consideration was set on 2nd May 2023, meaning this ticket really is due for a re-evaluation and ticket update. 

Atlassian team, any update on this?

+1

+1

524a15f45da9 I agree. It seems like Atlassian keeps acquiring new technologies that need further integration before finishing integration of technologies they've already acquired. Forms and Asset Management are still in a weird semi-beta state. The API for Forms is 'experimental' and SEVERELY lacking and forms don't even interact with an issue's history so changes to a form are possible without any audit trail. They push us to try these new features before they are fully integrated and then they seem to say, "Eh, good enough" and move on to the next thing. I wish they'd FINISH integrating the technologies they acquire before dedicating resources for the next new shiny thing, but that's the state of things at the moment. 

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.

This continues to be a thorn in not just my side but many of us.  

The only fields that can be used to manipulate the Issue Scope are a few system fields and another asset field.  A defined field with one value is a useless field, yet it is REQUIRED in order to pull in more information from the Assets Tables.

A default is necessary to be able to provide administrators the ability to:

• Filter asset values by Request Type (something that should be available but is not)
• Filter availability by other asset data related to a user or process (ie: Location)
• Filter list of Applications based on Type and/or Keyword (to limit the list shown to only the expected items)

There are many more examples, but this represents a few of the more critical ones

For the Atlassian team to understand a typical use case for this: 

Customers use Assets as their CMDB, including an object type that represents a concept such as 'Service offering' to represent the IT services offered to users on which they can raise service requests and incidents. 

Some forms will be generic and will allow the customer to select the Service Offering in the Request. 

But also common, are requests that are specific for 1 Service Offering. For these we need to be able to Add the Service Offering to the request, hide it and give it a default value. Example: a service request to 'Order a new Jira project' will need to have the Service Offering set to 'Jira Cloud' (hidden and preset). 

The work-around using an Automation works, but is indirect and more cumbersome to configure and maintain. 

Kind regards, Rik

This request has such a long timeline, and it seems like essential functionality for a lot of people. Has there been any movement on getting this implemented?