You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We are migrating from server to cloud.
used behavious to make fields mandatory during certain transitions mostly. but in cloud it works only on create screen not on transition screen.
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?
Not really, afaik. The limitations you currently see with behaviours are related to:
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!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.