Support Behaviour in Project's Issue Detail View#209

As a user, I want the Behaviour to also be applicable on the issue while viewing the issue in the Project’s Issue Detail View page (go to a Project, click ‘Issues’ in the sidebar, change to ‘Detail View’)

So that the same expected Behaviour outcome as seen in the Issue View is applied here as well. This helps make it more consistent.

What is the point of having the same behavior behaves differently if we are in the ticket summary (detail view) or in the ticket directly.
What is the point of having a Script runner behavior if it DOESN’T work everywhere?
People (customers) like me who have moved from Jira Software Server to jira cloud are very frustrated (and disappointed) by this.
The behaviors are used 20% in creation and 80% in edit view (wich include detail view)…. if you don’t solve this problem with Atlassian, many customers (like us) will not renew in the next years, it makes no sense to continue renewing the plugin if the main function for which we also bought it in the cloud IT DOES NOT do everything it should.
Even if it’s not your fault, you are the n1 partner of atlassian, there is no jira instance without scriptrunner…. so please make sure they expose the rest-api for the parts that do not currently work and implement the behaviors for the detail view.