alternative option for Behaviours

[prajakta_desai]

Hi Team,

We are migrating from server to cloud.

On Server 

  used behavious to make fields mandatory during certain transitions mostly. but in cloud it works only on create screen not on transition screen.

1.  For just mandatory fields without condition, works only create screen.( Used field  required validator on cloud )
2. If field mandatory with 2 or more condition in that case, we used Script runner scripts.
3. If field mandatory with  condition in that case, we used .field  required validator on particular transition on cloud )

but after migration  now we are facing one issue. on create screen we  don't have this fields.

- some behaviors mapped with all issue type. this issue types using diff. diff workflows. and associate with multiple projects. If we made changes in one workflow if will affect multiple projects and issue type. and that issue types and projects are not using this Behaviors.

- some behavours mapped with workflow. this  workflows using multiple issue types. .if we made changes in one workflow if will affect multiple  issue type. and that issue types not using this Behaviour

We can split the workflow, but can we have any alternative workaround fpr this?

[Walter Buggenhout]

Hi @prajakta_desai,

Not really, afaik. The limitations you currently see with behaviours are related to:

• what Atlassian allows / enables to be manipulated in the UI
• to the technological differences of the server / cloud platforms

So if you need to move now, embracing the limitations (and thankfully also the many available new capabilities too) is the way to go. That may in this case indeed boil down to creating separate transitions in the workflow with their own validators/conditions or working with separate configurations for different issue types.

Hope this helps!