Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Suggestion: Snooze for Jira tickets

Mohammad Norouzi
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Apr 06, 2023

Hi. We all faced those type of Jira issues that get blocked for some nasty blockers or we cannot proceed because of capacity, or perhaps some third party library is still incompatible and we are waiting for them to release which we don't know when that will be. Or maybe we just decide to give some tickets a rest for a few months.

The problem is that these tickets get lost, you know the saying out of sight, out of mind? 

It's hard to manage these tickets and you all done that when you keep moving them down the backlog and when we see them we surprisingly look at each other wondering  why such an important task is down there!

I think here a snooze functionality comes into picture. I love it in my GMail, when I get a bill email and I don't have time to pay it, then I snooze it to bring that up over the weekend. 

Or when I get that event ticket online and it's for next month, I snooze it to come back to my inbox 2 days before the event so I don't miss it. Believe me I missed some events just because I forgot it.

So for Jira, I can give you an example. We wanted to upgrade to Spring Boot v3.x.x but this library wasn't compatible so we said okay let's look at this in 3 months and check if they released a new version. But who's going to remember that in 3 months? I don't even remember what I had last night for dinner. 

Or many other tickets that are blocked.

Anyway, you now know what I'm talking about? A snooze functionality with some "hint" or "reminder message" that comes up at certain configured date/time and we can easily put that in the next sprint. That increases productivity and is very useful. What do you think?



Log in or Sign up to comment