Awesome Custom Fields for Jira Cloud

I'm using a cascading field, and I need to set the value in a loooot of issues. The workflow would be much smoother, if I clicked the field in the issue, and then the cursor / focus would be in the field already, so I can start typing right away. Instead, I need another click to put the cursor into the selection field.

Create a custom field that can be used as an Issue Lookup. single option selection or multiple option selection field. options in the custom field are based on a JQL statement - supported across JIRA project issue. the contents of the field must be searchable with JQL filters. The issue lookup custom field must be usable and supported in Automation rules.

Currently when using the customfields of "Awesome Custom Fields" the values are shown in the middle of the screen. Is it possible to relocate them more to the left like a normal field? This is basically for all customfields the same.

It would be great to get a new fieldtype for numbers which supports conditional formatting based on the value of the Input. Similar to the "Price Tag" just without the currency tag.

Need more colors for labels, not enough

Our agents are using some fields inside the JSM. We need to show some of them to user in read-only format without adding the new ones. Btw, we are using simple select and short text which are missing in the plugin.

As a jira Service Management User I would want more fields to add to a custom form for customers to give more nice looking value to a ticket that has been opened by a customer

I'm looking for a way to have a text field that searches previously entered text to match off of to prevent duplicate data when possible. This would be similar to how the Jira Component field works.

I have al large list with context fields options. I have to enter them by hand. I need a possibility to upload or paste them on edit options. Maybe this is possible with your custom fields solution?

Hello Team, could be possible to think about additionning different fields and putting the result in a "calculated field" ? Same thing about multiplying those fields ;-) Thanks !