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.
I’m Elyes, Product Manager at Elements.
To everyone and particularly Product Managers, I need your advice!
When designing a future feature, we conduct user interviews, create high & low-fidelity mock-ups to present to different people to gather feedback, and start writing and refining user stories once the scope has been defined.
For each story, we have acceptance criteria and acceptance tests, and sometimes sub-tasks when needed.
At last, when defects are found during the development process, bugs are created which block the story.
Now that you have the context in mind, let me tell you about my struggles.
It’s difficult for me to have all the relevant information at the feature level. When are the stories due date? In what version will each one be released? How can I see that a bug blocks the development of the story? I can go on and on…
Tell me I’m not the only one! What struggles do you face when designing features?
Hey @Pramodh M , thank you for your answer!
I was just wondering if a lightweight solution could do the trick.
Moreover, Gantt, Advanced Roadmap or BigPicture offer this kind of view at a global level right? Is it possible to display this kind of information at an issue level? Display all these information, but directly on the Epic.
Thanks again :)
Yes, we do have this at the Issue Level as well as per my understanding of Advanced Roadmaps.
It doesn't allow you to configure this at the issue level though, but at the global level and you can filter it it the issue level.
Let me know in case of any queries
Why are due dates important on story level?
I only have due dates for features. Based on the progression, you can decide which story or bug can be cut from the release.
As other mentioned above, I'd go with a Gantt chart where features are visualized.