Influence the roadmap: challenges with ScriptRunner Behaviours and migration

[Oleksii Kovalov]

Hi! I’m a product designer from Atlassian. My team is helping Adaptavist to move ScriptRunner Behaviours app to the cloud and we want to make sure that most important use cases are fulfilled by what we’re planning to work on.

I’m searching for Jira admins and alike who are working for organizations that:

1. Use ScriptRunner’s Behaviours feature.

2. Are planning their migration to the Cloud or already in the process.

3. Have problems with replicating their behaviours in app’s Cloud version.

If we’ll understand that your needs are not covered — we’ll adjust our roadmap to unblock you as soon as we can.

What's needed from you
To have a 1-hour call with me and our product manager or senior engineer, where we’ll talk about your organization’s needs and requirements related to ScriptRunner Behaviours.

If your organization is at least close to matching the criteria, please reply here or mail me at okovalov2@atlassian.com .

[Vedant Kulkarni]

Recently, we have finished the server to cloud migration and we struggled a lot for following features which was deployed on server with the help of Behaviors. We managed to find some alternatives however there is no exact solution yet.

1. Mark Epic Link field mandatory (*)
2. Hide/Unhide the field tabs

[Kris Buntinx]

We're in progress of a migrating to Jira cloud. We have a project on Jira server that heavily depends on behaviours. There are a few features missing in Behaviours for Jira Cloud that obstructs us from migrating to the cloud.

• We need to be able to use behaviours also in edit and transition views
• We also need behaviours to support date fields. Just simply be able to show and hide them.