I'm running Jira Server 7.9.2 and ScriptRunner 6.0.1.
I have a create/edit screen with 3 tabs.
Tab 0 has 2 required fields set in the field config.
Tab 1 and Tab 2 have fields that are dynamically required via a Behaviour.
While on Tab 0, ScriptRunner blocks the Submit or Update because we have required fields on Tab 1, which isn't currently selected and therefore is not visible to the user.
When the user is on a Tab that is completely filled out, but another Tab has required fields that still need to be filled out, how can I make that obvious to the user to switch to the Tab 1 to fill out the required fields before trying to submit?
In this screenshot, the 'Background Info' tab is complete, but the Software tab has required fields. There's no visual cue to the user to switch tabs to continue filling out required fields.
Hi @DH ,
We were having the same problem. I found out that this was already raised as a Bug with Adaptavist. The bug has been fixed in v6.9.0.
Bug SRJIRA-4332. So upgrading to this version or above should resolve your problem.
The Answer I came up with was not to use a behaviour to make them dynamically required.
Instead, I used a workflow 'simple scripted validator' which returns the user to the correct tab and highlights the field with a message of your choice, indicating to the user that the field is required.
Hello Community! I hope you've been enjoying the 🍂Apptoberfestivities🍂 (I know I have!) The event is heating up next week with a series of virtual events that we're calling the 🍻🍂Partner App ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events