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
Next: Root
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.
Hi,
I've setup a behavior mapped to a field named "quarter".
Depending on the quarter, a duedate is prefilled:
q1 -> june
q1 -> sept
q3 -> dec
q4 -> mar
Once running, it works ok on create screen cause as I select the quarter, the duedate gets filled automatically and I can still change the date as I want if needed.
The problem arises in the edit screen: in this screen, if the date was custom written, the behavior simply ignores that and overwrites it immediately with the automatic date according to the quarter chosen previously in the create screen.
This way I can lose the duedate without even noticing.
I know I can detect the screen whether it's the create or the edit one with below code, but how can I solve my problem ?
if (actionForm.contains("Create Issue") || actionForm.contains("Create") ) {
}
Is it possible to detect when the user actually choose a quarter (either a different one or the same that was chosen in the create screen) and in that case let the behavior assign the automatic value to the duedate ?