Timeline View time scale breakdown and dependency

[Kinane]

Hello there,

We've been using Jira's Product Discovery for a couple of months now, and we're very excited about the visibility it grants both the Product and Tech teams in addition to consolidating both workflows in the same place.

One important feature we're interested in as a Product team is to have a Timeline view with ideas breakdown.

The timeline view offers two time scales, monthly and quarterly, which make sense. But we find it hard to tell which idea would be tackled first within a month for instance.
Say two Ideas are expected to be delivered in a given month. In the current timeline view, these two ideas are stacked one on top of the other and spans the entire month, when in reality one only takes a week to deliver and the other 2 weeks, for the sake of the example.

1. Is there a way to reflect the true start and end date of the idea on the Timeline?
None of these two posts, this and this clarify whether this is possible.

2. Is there a way to have ideas that blocks other ideas visually reflect said dependency on the Timeline?

3. Is it possible, that in the case of one idea blocking another, whenever the depended on idea is moved on the Timeline all its depending ideas would also be move accordingly?

4. Is it possible to limit the ideas that can be added to a timeline view to those available in one or more boards in particular? e.g. now, later or someday?

I think the above functionalities are essential to any proper timeline management solution.

Last but not least, is there a place where we could check what features to come next and when to expect them?

Looking forward to hearing from you.

Thanks.

[Michael G_]

Adding a comment in support of the second suggestion here, to visualize the dependency lines in the timeline view. It would really be beneficial for our roadmap if we could easily keep track of dependencies across initiatives.

[Rohan Swami]

Hi @Kinane,

The timeline is intended to present a very high level view, hence it deliberately does not reach the precision of weeks. I appreciate the feedback and we'll take this on board.

The features you're describing seem to be closer to a detailed delivery planning roadmap tool. I would recommend Basic Roadmaps in Jira Software, this does everything you mentioned: https://www.atlassian.com/software/jira/features/roadmaps?tab=basic

We currently don't have a live page with upcoming features, we share announcements of new features in Community posts. Our focus at the moment is progressing from Beta to General Access which will include: Sharing views with your stakeholders, collecting ideas from your stakeholders, and a whole heap of regulatory and compliance features.

[Kinane]

Hi @Rohan Swami ,
Thank you for your reply.

I am aware of Jira Software Roadmap, but unfortunately we don't find it to be a good fit in this case for the following reasons:

1. It lives in a different project, not within Product Discovery. Which mean in the case of a user not using Jira Software, said user will have to create and maintain epics, stories, etc. on Jira Software only for the sake of having the timeline view. An overhead in my opinion.
2. There is a sort of disconnect between Product Discovery and Jira Software "issue" types. In Jira Discovery the only available issue type is idea, which can easily be mapped to a story or task in Jira Software, but not to an Epic, which the Roadmap supports.
   I find a need in Product Discovery to have a more abstract type of issue that can map to Jira Software Epics, for instance a goal/target/objective of some sort that many ideas put together would contribute to. Only then, epics could be leveraged in the Roadmap for that purpose, although still at the condition/inconvenience of using Jira Software too.
3. Product and Tech timelines might very well be different, I think a separation between the two is best.

Just to recap my concerns. I am pretty happy with the monthly or quarterly scale of Product Discovery's timeline view what is inconvenient though is:

1. An idea spans an entire month, even though it start and end date spans for a couple of days or weeks.
2. The lack of dependency management.

I understand that Product Discovery is in Beta, I just hope that the community feedback is taken into account in future versions.
And that an alternative, even if not the most convenient, is available to leverage the desired outcome of a timeline view.
Visibility on a product level.

Thanks again.

[Rohan Swami]

Thanks @Kinane we'll take your feedback on board. It's still early days for Jira Product Discovery, there's plenty more to come and we're excited to bring it to you!

[Alexander Czechowski]

Upvote on #1!

We'd like to be able to see the timeline on a weekly (or 2-week) timescale in order to give a truer depiction of when work is likely to happen. The biggest concern that our Jira Discovery board has created within our org is when we know something is starting toward the end of the month, so we include the current month and next month, and then it makes it looks like we're investing 2 months into it, where it may only be 2 weeks. This is where a weekly (or 2-week) view would help correct that misinterpretation.

[Meghan LaClair]

Hey @Kinane  - I haven’t had a chance to look at Jira Product Discovery yet but it sounds like what you are looking for is already available in our Predictive Roadmap at minware. Take a look at the screenshot below (heads up it’s old, we’ve gone through major changes) and let me know if you want to check it out!

Disclaimer: Marketplace Partner