I am trying to use the Behaviours plugin to display and require a field on a transition screen based on the input of a field that was populated on the create screen or edited at anytime in the workflow, but the behaviour is only working for the field on the edit/view screen.
If a user selects "Waved" from a checkbox field when creating or editing a ticket, the "Work Started Date" field should display on a specific transition screen, but it does not.
I have mapped to the associated workflow and configured a condition for that specific transition, but still no luck.
The field does not display if "Waved" is selected or not.
If I do not use the condition, then the field becomes does display on the edit screen, but it is also required, which I do not wish to happen because the field doesn't need to be required until the specific transition in the workflow is reached.
Anyone have any thoughts, ideas or suggestions?
You may wish to look at the documentation on Transition Screens located here as this may give you some pointers on how to achieve your requirement.
If you still require help can you please post your script and details of how you configured it here so that we can look to help you further.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
In this post you will discover more about the evolution of K15t software, some big topics they're currently focusing on in the app space, and a rare (not not funny!) photo of founders Mike Cannon-Bro...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs