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.
My issue type has many fields on few tabs, including a custom field date type on tab 2.
When the user edits the date we need a behavior to check and set another custom field. This works fine.
From the View screen if they try to directly edit the date, the Edit screen pops since that is how behaviors work. Executing `switchTab(2)`takes them to the correct tab and the field has focus. Beautiful.
What I need is a way to differentiate when they do this, versus simply clicking the Edit button to open the edit screen to change another field. When that happens right now the behavior fires and tab 2 is displayed.
How can we test the special case where the user want to edit a field from a behavior versus simply edit the issue?
I hope this is clear, thanks!
I do not believe that it is possible from a behaviour initialiser script to detect if the screen was opened by clicking the edit button or attempting to open an in-line edit.
IMO, this should be built-in and you should not have to code the tab change.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.