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.
Is there a reason why when changing a previously saved filter, you have to run the search before it can be saved? I do find it a little annoying. Why not just let me save the change with a single keystroke?
OK thanks Nic. I just seemed a little silly when all I was doing was adding another status to my query, but I get it.
I know, it does seem like the syntax check should be enough to enable the save button, and for a lot of us, it probably is. But there are enough people in the minority who inadvertently write bad JQL to justify a quick test before saving. (I'm in that minority by the way - I get over-confident about my JQL skills sometimes, and it's a nice reminder that I'm not that good...)