Skip to main content
Open

Timeline: Jira Cards. Group by Parent/Link Hierarchy

Related products:Apps & Integrations
  • May 12, 2025
  • 3 replies
  • 108 views
F

When using Jira cards within the Timeline app, there are multiple ways of grouping tickets - eg Status, Assignee, Start Date, etc. There is no way to group tickets by their hierarchy - eg Initiative, Epic, Task, Subtask.

It would be beneficial to be able to do so as this would automatically reflect the ability with Jira’s “Structure” plugin - which is built off both Parent and Link fields.

This combination of fields to produce the hierarchy is important as companies using Jira Basic use the links to work around the limitation of 3 levels of hierarchy at this Jira tier.

The end result is enabling Timeline to reflect groupings similar to Structure so that this view can be presented on a canvas with other relevant project works.

 

As a stretch goal, displaying Dependency linkages within the Timeline app would also be highly beneficial so as to ensure the correct order of tasks arranged on the Timeline.

3 replies

Eca
Mironeer
Forum|alt.badge.img+2
  • Eca
  • Mironeer
  • May 13, 2025

Thanks so much for taking the time to submit this idea, ​@Ferg ! Our team will review this and it’s open for votes and comments. 

 

For those coming across this idea, if you feel this would be helpful for you or your business, please be sure to vote for it and leave a comment about your use case to help our team scope this request!

Thank you again for helping make Miro better!

Eca :)
E
  • Ethan Koltz
  • New Here
  • August 29, 2025

This should be a requirement for this feature for studios working at any scale. 

F
  • Ferg
  • Author
  • Beginner
  • October 27, 2025

Heh.  I’d forgotten I’d raised this a few months ago - it’s been a busy year - and came looking to see if the community had any ideas.  

Please take this as a reiteration that it would be a great addition to how Jira cards work. 😁

While Jira Planner in Miro is great to import tickets and the like, it is a little hamstrung by needing to have a Jira Board to associate with.  The way Tempo’s Structure works is that it crawls all the linked items (Initiative, Epic, Stories, Task, Sub task, etc etc) and so pulls all related items in.  Relying on a Jira Board means you’re likely to need a Jira Premium license for the query to be useful - else you need to manually add Epics to the query to build the board.

Miro’s Jira Table, Kanban & Timeline are also great, but lack the ability to import.

Ideally, I’d like to

  • feed an Initiative into the tool
  • have it find all the linked items in a downward direction
    • note that hierarchy won’t always fit the bill as Jira Basic has Epic as top level, and Initiative is therefore a linked item
  • place a restriction on depth (default ‘all’ levels)
  • drag and drop these in any one of the above tools to change the date, status, etc, and have that reflect auto-magically in the other boards and in Jira.
    • Likewise, any modification in Jira is pushed to the boards (I believe this has been improved since we implemented it, however I need to convince our IT team we need to re-do the integration to make it work properly)
  • Ideally, collapse and expand levels on a per work item basis (eg collapse sub-tasks so only the task is visible, or tasks so the Epic is visible.)
    • The purpose of this is to remove/control the amount of clutter on the board at any one time.

The intent is to be able to give teams the ability to focus on smaller parts of work, say from the Epic level down, while Delivery Leads and Product Owners can use it to see the bigger picture.

I imagine ‘Focus’ would be something we’d leverage in this solution too.

As of this writing, I see there’s only 4 votes, so I won’t hold my breath. But, don’t ask, don’t get!

Many thanks Miro team!

Terms & ConditionsAccessibility statement