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
What triggers you to check it: a follow-up email, Slack messages, the general roadmap, or a deadline? What do you primarily observe to get a response to your question? In my experience, I do this almost daily. It has become almost the main source of truth for me. We use Epics as projects. What has been your experience with this?
Hi @Mariam Matiashvili -- Welcome to the Atlassian Community!
IMHO, this depends on the team and product owner's (PO) working methods...and the different scales at which you are looking for information. As a PO, please consider what do you want to know, why that information, how would you want to see it / use it, and when do you need to know it?
Some of these can be supplemented using Jira Product Discovery, roadmaps / timelines, dashboards, and the Jira reports. Again, please consider your and the team methods to consider what is helping and where things can be improved...and then discuss that with the team to define experiments to improve.