Alternative to Behaviors in Jira Cloud for JSM projects.

[Pedro Morocho]

Is there an alternative to ScriptRunner in Jira cloud for JSM type projects since Behaviors are not compatible with this type of project and there is no way to do anything about the creation screens?

[Nic Brough -Adaptavist- · Accepted solution]

Welcome to the Atlassian Community!

I am not aware that Behaviours for Jira Cloud has any competition (if we did, the SR team would be talking about it in most of my meetings).

Behaviours (and the rest of Scriprunner) is heavily limited by the Cloud framework, and it's taken a long time, and a lot of work with Atlassian, to get it to be able to work on Cloud. 

Even if there were a competitor, the best they could do is re-implement Behaviours (with a different admin interface maybe).   They would not be able to do anything that Behaviours does not yet do - they'd be limited in the same way Behaviours is by the Jira platform. 

We are still working with Atlassian to get the extension points we need to enable Behaviours to do more.  It does actually work on JSM projects, but only on the "create issue" screen, but Im pretty sure you want to use it on the "create request" screen.  That is on the to-do list.

[Erki Jolla]

Any news or updates on when we could expect a breakthrough with Atlassian to get Behaviors for JSM Cloud?

[Deiser Service Team]

I don't really find how it works on JSM projects, if you cannot set a specific project into the scope. I only want to set hidden and required fields, nothing really complicated, but I cannot select the project.

If there is any kind of way to configure that on JSM projects, it would be nice.

Regards.

[Fabian Lim · Accepted solution]

Hi @Pedro Morocho

What exact functionality of behaviors are you looking for?  

Regards,

Fabian

[John Funk · Accepted solution]

Hi Pedro,

First, no there isn't. 

Second, what are you trying to do that you need Behaviours for?

[Pedro Morocho]

I am trying to replicate the behavior of the behaviors of a data center version for a Jira Service Management project that migrates to the cloud, but apparently in the cloud version you cannot modify the screens, as such you cannot interact with the fields (edit, delete, create).

[John Funk]

You might be able to use forms for the create process to do some of that. 

[G_M]

Hello Atlassian Community!

I would like to refine the requirements for JSM Behaviors, as their use has not been clearly defined to date. (See also Fabian Lim´s request)

We work extensively with behaviors for the following purposes (classic front-end logic):

Validating business logic

For example, fields are shown or hidden depending on the selection of certain options (e.g., option fields or asset fields).

Or

When filling out one field, other fields become mandatory

Usability functions

We already show Jira customers transparently in the UI which URL has which Confluence SpaceKey or which contact person (SpaceAdmin) will interact with them here.

Or

we transparently calculate the summary when entering/filling in fields in order to generate uniform summaries.

These are all scenarios that can be solved without behaviors. However, these are then opaque, even bordering on “black magic.”

Implementation in different customer request types is only conceivable if a new customer request type is created for each business logic rule.

JSM behaviors are

• easy to implement
• significantly more user-friendly

They have certainly proven their worth in the DataCenter.