Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-91572

Option to drill down to the Subtask level in the Timeline (Formerly Roadmap)

    • 5,736
    • 85
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem Definition

      After implementing JSWCLOUD-17442 the option to drill down to stories was added to the roadmap but the ability to see the subtasks of those stories is not avaliable so at the moment hiding details useful to the roadmap view as you cannot see the subtask issue below the stories in the roadmap

      Suggested Solution

      Enable seeing the child Subtasks alongside Epics and Stories in the roadmap for the full hierarchy visibility


       

      Update on 22 January 2024

      Hi all,

       

      We are reviewing this request at the moment and will provide a follow-up in a few months time. We understand that especially with the recent release of subtasks support in backlog, there is a higher interest for subtasks to be made visible in Timeline.

      At the time being, as some of you have noted in the comments below - you can use Timeline inside Plans for this purpose. Plans can take a single or multiple projects, boards, and filters as their issue sources and display the relevant Jira issues, including subtasks.

      Plans are available for Jira Premium (https://www.atlassian.com/software/jira/premium) . You can learn more about Plans here: https://www.atlassian.com/software/jira/guides/advanced-roadmaps/overview#what-is-advanced-planning . Just head over to the “Plans” menu item on top navigation in Jira to give it a go.

       

      Thank you for your patience on this request.

       

      Regards,

      Irene Ongkowidjaja

      Senior Product Manager

       

       

       

      Update from Jira Software Cloud team on 31st August 2022

      Thank you for your valuable feedback. We hear your concerns.

      _After the recent release of displaying story/task level issues on the timeline in Kanban projects, we can now assess this request appropriately. https://community.atlassian.com/t5/Jira-Software-articles/What-s-new-in-the-Roadmap-view-I-m-so-glad-you-asked/ba-p/2077594_

      When commenting or voting on this ticket, we are always interested to know the "why" behind your team's need for the ability to drill down or plan on this granular level with sub-tasks, or what context you or stakeholders are missing by not seeing any information related to subtasks. 

      _We appreciate your insights - and if you would like to chat in detail about this,  feel free to reach out to the team directly: jira-cloud-roadmaps@atlassian.com

      Thanks, 
      Rathesh Richards, Product Manager, Jira Software Cloud_

       

            [JRACLOUD-91572] Option to drill down to the Subtask level in the Timeline (Formerly Roadmap)

            Please make subtasks in timeline visible

            Uta Monika Nolte added a comment - Please make subtasks in timeline visible

            Please add this

            Martin Vali added a comment - Please add this

            Please add this

            Janice Waddick added a comment - Please add this

            Please someone can do this?

            nuno.ferreira added a comment - Please someone can do this?

            Patrik Štoural added a comment - - edited

            Dear Jira team,

            This feature would help us greatly, and you already have it in Jira Work Management. So why don't you have it in Jira Software?

            Screenshot: https://ibb.co/FqWX4nbp

            Patrik Štoural added a comment - - edited Dear Jira team, This feature would help us greatly, and you already have it in Jira Work Management. So why don't you have it in Jira Software? Screenshot: https://ibb.co/FqWX4nbp

            I understand that for Atlassian this is a business imperative to differentiate standard and premium licenses. It would be great having subtasks in timeline at least when you have premium licenses because advanced roadmaps are, as its own name indicate, advanced: it has a lot of useful functionalities but also it is quite more difficult to use than a simple timeline view.

             

            Antonio Valle (G2) added a comment - I understand that for Atlassian this is a business imperative to differentiate standard and premium licenses. It would be great having subtasks in timeline at least when you have premium licenses because advanced roadmaps are, as its own name indicate, advanced: it has a lot of useful functionalities but also it is quite more difficult to use than a simple timeline view.  

            For now I'm using the list function on the board. This can also display subtasks. It is also not necessary to synchronize changes. The planner, on the other hand, can display several projects at the same time.

            Hendrik Gerike added a comment - For now I'm using the list function on the board. This can also display subtasks. It is also not necessary to synchronize changes. The planner, on the other hand, can display several projects at the same time.

            bb3b5f443b59 would be great to get an update on those  
            Especially now, when I can also have sub-tasks in Plans and subtasks in Lists, it feels like Sub-tasks on the Timeline view in the Board is a big missing component.

            Mateusz Janczewski added a comment - bb3b5f443b59 would be great to get an update on those   Especially now, when I can also have sub-tasks in Plans and subtasks in Lists, it feels like Sub-tasks on the Timeline view in the Board is a big missing component.

            🎂🎂🎂

            Hello,

            Last update on this was just over 1 year ago, happy birthday! Could we please get the update that was promised "in a few months time"?

            With over 1600 votes there is clearly demand for this feature.

            Thanks
            Joe

            Joe Johnson added a comment - 🎂🎂🎂 Hello, Last update on this was just over 1 year ago, happy birthday! Could we please get the update that was promised "in a few months time"? With over 1600 votes there is clearly demand for this feature. Thanks Joe

            +1 

            +1

            Sebastian Kley added a comment - +1

            Dear Jira team,

            we have started evaluating Jira as our project mgmt tool, but in absence of the sub-tasks showing up on timeline the sub-task function is of negligible benefit. Creating tasks and stories just to bring these on timeline is a huge negative. Is there any other feature in standard plan to activate it? 

            Swapnil Gonsalves added a comment - Dear Jira team, we have started evaluating Jira as our project mgmt tool, but in absence of the sub-tasks showing up on timeline the sub-task function is of negligible benefit. Creating tasks and stories just to bring these on timeline is a huge negative. Is there any other feature in standard plan to activate it? 

            Kelsey Mortimer added a comment - - edited

            Agree with all the comments.  Sub-tasks not being in the timeline view to expand along with Epics and Stories means my developers have trouble finding them and we end up with them creating "stories" that are really sub-tasks because they don't realize they are there when multiple devs are collaborating across a single story under an Epic.  The work around it to make Stories Epics which defeats the entire purpose of the hierarchy.  3 levels in all views is helpful.

            And we shouldn't have to pay for Plans and leave our boards to get visibility to our work items that are already in the system.  That just makes it more difficult for everyone.

            Kelsey Mortimer added a comment - - edited Agree with all the comments.  Sub-tasks not being in the timeline view to expand along with Epics and Stories means my developers have trouble finding them and we end up with them creating "stories" that are really sub-tasks because they don't realize they are there when multiple devs are collaborating across a single story under an Epic.  The work around it to make Stories Epics which defeats the entire purpose of the hierarchy.  3 levels in all views is helpful. And we shouldn't have to pay for Plans and leave our boards to get visibility to our work items that are already in the system.  That just makes it more difficult for everyone.

            +1

            +1

            +1

            +1

            Marco Zanotti added a comment - +1

            Benjamin added a comment -

            ++

            Benjamin added a comment - ++

            Manuel added a comment -

            Same here, please add subtasks to the timeline.

            • This reminds me of the Reporter field, which was missing in Advanced Roadmaps for quite some time. 
            • Then it was available all of a sudden. 
            • Who would ever come to the conclusion (at feature definition) that Reporter is so irrelevant that it would not even be available within Roadmaps?!?

             

            Manuel added a comment - Same here, please add subtasks to the timeline. This reminds me of the Reporter field, which was missing in Advanced Roadmaps for quite some time.  Then it was available all of a sudden.  Who would ever come to the conclusion (at feature definition) that Reporter is so irrelevant that it would not even be available within Roadmaps?!?  

            Benjamin added a comment -

            I join 94bcb125c2cc . Please please please do something to display sublevel tasks. Without the possibility they are completely useless.

            Benjamin added a comment - I join 94bcb125c2cc . Please please please do something to display sublevel tasks. Without the possibility they are completely useless.

            I add (again) my voice to this request. Could the Jira Team provides us an update (nothing new since ** the 22 January 2024) ?

            Until now, I don't recommand Jira Cloud around me, and always speak about this example of lack of answer. I think you could earn a lot of customer fidelity by answering this kind of issue.

            Regards.

            Eric Guichaoua added a comment - I add (again) my voice to this request. Could the Jira Team provides us an update (nothing new since ** the 22 January 2024) ? Until now, I don't recommand Jira Cloud around me, and always speak about this example of lack of answer. I think you could earn a lot of customer fidelity by answering this kind of issue. Regards.

            Continuing to echo other users - this should be a very basic feature. Why is there no urgency to make this a function in the timeline view? Even moreso, not to have an update since the beginning of this year seems a bit ridiculous. 

            Gabrielle Hitchcock added a comment - Continuing to echo other users - this should be a very basic feature. Why is there no urgency to make this a function in the timeline view? Even moreso, not to have an update since the beginning of this year seems a bit ridiculous. 

            Echoing and agree - The timeline view provides little value without being able to schedule and view below Story level. This basic use case does not seem to align with a premium feature tier. Please make this change it would improve Jira into being a better development and project management tool.

            Jeremiah Thompson added a comment - Echoing and agree - The timeline view provides little value without being able to schedule and view below Story level. This basic use case does not seem to align with a premium feature tier. Please make this change it would improve Jira into being a better development and project management tool.

            Steve Blum added a comment -

            I agree with many others here: Timelines not showing subtasks makes them unusable for all non-trivial projects. Its beyond me why people had to invest time to implement Timelines in the first place, if such a trivial feature wasn't implemented in over 4 years. 

            Steve Blum added a comment - I agree with many others here: Timelines not showing subtasks makes them unusable for all non-trivial projects. Its beyond me why people had to invest time to implement Timelines in the first place, if such a trivial feature wasn't implemented in over 4 years. 

            Only allowing this to be available for timeline on plans (which requires a premium subscription) is not acceptable. This should be available within normal Jira Work Management Timelines.

            Joseph Orellana added a comment - Only allowing this to be available for timeline on plans  (which requires a premium subscription) is not acceptable. This should be available within normal Jira Work Management Timelines.

            Adding my support on this, after spending a fair amount of time fiddling with my timeline settings to try to get my child subtasks to show up. Not being able to see them in the timeline seems such a basic and essential feature for scheduling. Please make it happen 

            Russell Young added a comment - Adding my support on this, after spending a fair amount of time fiddling with my timeline settings to try to get my child subtasks to show up. Not being able to see them in the timeline seems such a basic and essential feature for scheduling. Please make it happen 

            Echoing and agree - The timeline view provides little value without being able to schedule and view below Story level. This basic use case does not seem to align with a premium feature tier.

            Kevin Schatz added a comment - Echoing and agree - The timeline view provides little value without being able to schedule and view below Story level. This basic use case does not seem to align with a premium feature tier.

            +1

            it is confusing to users as next-gen Business Projects (formerly Jira Work Management projects) support this

            ヴァリエンテ フロリアン(Florian Valiente) added a comment - +1 it is confusing to users as next-gen Business Projects (formerly Jira Work Management projects) support this

            Sub-tasks on the timeline is a must. I don't understand how this can stay open for 4-5 years without so much as an update.

            Lasse Wathne Lorentzen added a comment - Sub-tasks on the timeline is a must. I don't understand how this can stay open for 4-5 years without so much as an update.

            Dear Jira Team,

            Thanks for the fabulous product. But I am wondering does it take 4.5 years to consider a change so much needed and being supported by other products in the market? Unbelievable!!!

            Vishal Thakur added a comment - Dear Jira Team, Thanks for the fabulous product. But I am wondering does it take 4.5 years to consider a change so much needed and being supported by other products in the market? Unbelievable!!!

            Isai Navarro added a comment - https://getsupport.atlassian.com/browse/JST-1014572

            Shirley Song added a comment - - edited

            Timeline feature in Jira is great, adding subtasks will make life easier for everyone. Specifically if they are child of parent tasks already in the timeline. We can hide non associated subtasks but parent related ones would be very helpful.

            Shirley Song added a comment - - edited Timeline feature in Jira is great, adding subtasks will make life easier for everyone. Specifically if they are child of parent tasks already in the timeline. We can hide non associated subtasks but parent related ones would be very helpful.

            Please add sub-task to Timelines just as you did for the backlog

            Steve Michel added a comment - Please add sub-task to Timelines just as you did for the backlog

            Petr AST added a comment -

            Can someone tell me, with the release of displaying subtasks in work management projects timelines, are there any plans to release this feature into Software projects?)))

            Petr AST added a comment - Can someone tell me, with the release of displaying subtasks in work management projects timelines, are there any plans to release this feature into Software projects?)))

            Christopher Favreau added a comment - - edited

            Having sub-tasks on the timeline will make the timeline useful.  Right now it is not useful (as in I do not use the timeline) because you cannot see all of the work on the timeline so sub-tasks cannot be scheduled like the other types can.

            If someone responsible for scheduling features please make sub-tasks visible and work on the timeline.

            Maybe this feature is a sub-task and it doesn't get scheduled because you cannot see it on the timeline.

            Christopher Favreau added a comment - - edited Having sub-tasks on the timeline will make the timeline useful.  Right now it is not useful (as in I do not use the timeline) because you cannot see all of the work on the timeline so sub-tasks cannot be scheduled like the other types can. If someone responsible for scheduling features please make sub-tasks visible and work on the timeline. Maybe this feature is a sub-task and it doesn't get scheduled because you cannot see it on the timeline.

            Hi,

             

            one more vote from my side - is one of the reasons why we avoid using subtasks.

            Emilia KASPRZYK added a comment - Hi,   one more vote from my side - is one of the reasons why we avoid using subtasks.

            Aaron Sonday added a comment - - edited

            We need this feature for cross-functional team planning on a quarterly timeline in Software projects. 

             

            Aaron Sonday added a comment - - edited We need this feature for cross-functional team planning on a quarterly timeline in Software projects.   

            So why is this feature not yet available? It is very useful and I can't imagine why it would take so ling to integrate in Jira cloud. Please release this soon!

            jan.engelke added a comment - So why is this feature not yet available? It is very useful and I can't imagine why it would take so ling to integrate in Jira cloud. Please release this soon!

            Chloe Evans added a comment - - edited

            This ticket as well as several other tickets and documentation indicates that you can view Subtasks on the Premium version in the Plans feature. I have the Premium license and am using Plans and am not able to expand the heirarchy to drill down to the subtask level. I can't find any clear documentation or settings that would enable this level of drill down either.

            The only thing I can see related to subtasks is start and end date bars inherited on the Task level for subtasks beneath them with no way to actually view or drill down to the subtask that has those dates assigned. This is very misleading and also not very helpful at a detailed level. I find it easier to view and navigate to subtasks on the traditional Timeline because at least there I can click on the Task and view the subtasks in the preview screen on the right. I'm using a traditional Epic > Task > Subtask heirarchy so why is this not displaying the full heirachy in Plans Premium version as is indicated here?

             

            EDIT: I finally found how to enable Subtask drill down in Plans. It's under the Filters option at the top, you can set the Heirarchy to Epic to Subtask. For some reason it's not set up this way by default and I really had to dig and just stumble upon it to figure this out. This could be way better documented.

            Chloe Evans added a comment - - edited This ticket as well as several other tickets and documentation indicates that you can view Subtasks on the Premium version in the Plans feature. I have the Premium license and am using Plans and am not able to expand the heirarchy to drill down to the subtask level. I can't find any clear documentation or settings that would enable this level of drill down either. The only thing I can see related to subtasks is start and end date bars inherited on the Task level for subtasks beneath them with no way to actually view or drill down to the subtask that has those dates assigned. This is very misleading and also not very helpful at a detailed level. I find it easier to view and navigate to subtasks on the traditional Timeline because at least there I can click on the Task and view the subtasks in the preview screen on the right. I'm using a traditional Epic > Task > Subtask heirarchy so why is this not displaying the full heirachy in Plans Premium version as is indicated here?   EDIT: I finally found how to enable Subtask drill down in Plans. It's under the Filters option at the top, you can set the Heirarchy to Epic to Subtask. For some reason it's not set up this way by default and I really had to dig and just stumble upon it to figure this out. This could be way better documented.

            Ben Saar added a comment -

            Im shocked this is still open

            Ben Saar added a comment - Im shocked this is still open

            david.don added a comment -

            subtasks are a must have if we are going to use timeline feature in JIRA.

            david.don added a comment - subtasks are a must have if we are going to use timeline feature in JIRA.

            Peter Hill added a comment - - edited

            As a Project Manager working with software teams in JIRA, it is absolutely non-sensical that ALL tasks, regardless of type, are not visible on a Timeline. This is just the most basic, basic, project management 101 requirement to make any timeline feature of any value at all. That this is something that Jira product managers do not accept shows that you don't really understand project management. 

            I get it, software developers like to work differently, Agile is more flexible, blah blah blah. But that doesn't mean they have to have invisible tasks that disappear on a timeline! That is just absurd.  

             

            Peter Hill added a comment - - edited As a Project Manager working with software teams in JIRA, it is absolutely non-sensical that ALL tasks, regardless of type, are not visible on a Timeline. This is just the most basic, basic, project management 101 requirement to make any timeline feature of any value at all. That this is something that Jira product managers do not accept shows that you don't really understand project management.  I get it, software developers like to work differently, Agile is more flexible, blah blah blah. But that doesn't mean they have to have invisible tasks that disappear on a timeline! That is just absurd.    

            Hey all,

            Is there any other existing (e.g. without a paid upgrade) way to visualize subtask's dependencies that I'm not aware of? Because in Timeline, I can visualize the dependencies between Tasks and Stories. However, if the dependency is able to be made, I would believe that it should be able to be visualized as well, which is not the case for subtasks, I don't think. Please let me know if I'm mistaken. Thanks!

            Andrew Cziryak added a comment - Hey all, Is there any other existing (e.g. without a paid upgrade) way to visualize subtask's dependencies that I'm not aware of? Because in Timeline, I can visualize the dependencies between Tasks and Stories. However, if the dependency is able to be made, I would believe that it should be able to be visualized as well, which is not the case for subtasks, I don't think. Please let me know if I'm mistaken. Thanks!

            Still waiting

            Lisa Vanderbeck added a comment - Still waiting

            Everybody still waiting Atlassian

            Marcelo Lourenco added a comment - Everybody still waiting Atlassian

            MJ added a comment -

            ....still....still...waiting. I had to also turn all my subtasks to tasks. 

            MJ added a comment - ....still....still...waiting. I had to also turn all my subtasks to tasks. 

            Tomorrow it will be the birthday of this ticket, opened on January 16th, 2020. I still cannot believe Atlassian has not fixed this problem and is causing teams so much trouble. I had to turn all my subtasks into tasks to use the timeline properly and keep stakeholders truly updated and with enough visibility. 

            Atlassian when are you going to do something about this?

            Guelmis Martínez added a comment - Tomorrow it will be the birthday of this ticket, opened on January 16th, 2020. I still cannot believe Atlassian has not fixed this problem and is causing teams so much trouble. I had to turn all my subtasks into tasks to use the timeline properly and keep stakeholders truly updated and with enough visibility.  Atlassian when are you going to do something about this?

            David Holman added a comment - - edited

            Jason Carothers, I've used Plans for this as well where the client already has Jira Premium. It works much better than the default behavior.

            But if you're on standard Jira, the upgrade cost is pretty stiff for this basic functionality. To get better planning visibility for less total investment, I'm using Productboard. That gives me views that I can share to the rest of the business as well, without extra licenses.

            In the end, I find that I'm being more and more conservative with my Atlassian commitments because of all the little frustrations like this ticket. The less I depend on Atlassian, the better my team's experience and the quicker I can pivot when the time comes.

            David Holman added a comment - - edited Jason Carothers, I've used Plans for this as well where the client already has Jira Premium. It works much better than the default behavior. But if you're on standard Jira, the upgrade cost is pretty stiff for this basic functionality. To get better planning visibility for less total investment, I'm using Productboard. That gives me views that I can share to the rest of the business as well, without extra licenses. In the end, I find that I'm being more and more conservative with my Atlassian commitments because of all the little frustrations like this ticket. The less I depend on Atlassian, the better my team's experience and the quicker I can pivot when the time comes.

            Jason Carothers added a comment - - edited

            So... after years of frustration on this and seeing countless comment after comment of everybody experiencing the same. A breakthrough. Not sure which actual product/SKU "Plans" are under as far as what license you have to have - but in the Timeline under Plans you can do this really cleanly. Finally. Finally we have roadmaps down to the subtask level. Mockup below, blue issues in the blur out are subs and if they had dates they would show on the right too... granted there is no good "print view" or ability to zoom out to see the entire timeline but it's a start. Well I guess it looks like I can paste a screenshot, but then I get an error saying I don't have permission to add an attachment sorry. 

            Jason Carothers added a comment - - edited So... after years of frustration on this and seeing countless comment after comment of everybody experiencing the same. A breakthrough. Not sure which actual product/SKU "Plans" are under as far as what license you have to have - but in the Timeline under Plans you can do this really cleanly. Finally. Finally we have roadmaps down to the subtask level. Mockup below, blue issues in the blur out are subs and if they had dates they would show on the right too... granted there is no good "print view" or ability to zoom out to see the entire timeline but it's a start. Well I guess it looks like I can paste a screenshot, but then I get an error saying I don't have permission to add an attachment sorry. 

            The limit of 2 levels force me to switch to on another tool more powerful then timeline. Once switched I create the items there so Jira tool loose the driver role in the department tools asset

            Luciano.Serino added a comment - The limit of 2 levels force me to switch to on another tool more powerful then timeline. Once switched I create the items there so Jira tool loose the driver role in the department tools asset

            No need to add any more detail to this request than what has already been requested by everyone below! Please add this feature, subtasks are pretty much useless without it. Thanks

            Donal Smith added a comment - No need to add any more detail to this request than what has already been requested by everyone below! Please add this feature, subtasks are pretty much useless without it. Thanks

            You shouldn't allow a field to make an subtask if you can see it in the timeline.  Please fix this.  Will it take that much effort?  Or did it in itself generate that much revenue?  I would think pleasing my customers would generate more income by adding more value.

            Robert Janes added a comment - You shouldn't allow a field to make an subtask if you can see it in the timeline.  Please fix this.  Will it take that much effort?  Or did it in itself generate that much revenue?  I would think pleasing my customers would generate more income by adding more value.

            Chris Chipman added a comment - - edited

            Whats really funny about this one - it really should have been there all along. Its completely a no brainer. And this issue has been here festering for just how long now?
            BASIC FUNCTIONALITY REQUEST: "Hi there! Are we ready yet?"
            ATLASSIAN(Three years later): "Still trying to decide if you are really needed. Please hold."

            Chris Chipman added a comment - - edited Whats really funny about this one - it really should have been there all along. Its completely a no brainer. And this issue has been here festering for just how long now? BASIC FUNCTIONALITY REQUEST: "Hi there! Are we ready yet?" ATLASSIAN(Three years later): "Still trying to decide if you are really needed. Please hold."

            Use case: I dont have premium and our organization will not invest in it. The subtasks show the actual work that we are doing on the tasks and tracking the target dates on those subtasks helps roll up to assessing the health of our overall timelines on kanban projects.

            Jamie Brennan added a comment - Use case: I dont have premium and our organization will not invest in it. The subtasks show the actual work that we are doing on the tasks and tracking the target dates on those subtasks helps roll up to assessing the health of our overall timelines on kanban projects.

            Currently 4th highest votes for a feature request, please add it Atlassian.

            richard.jackson added a comment - Currently 4th highest votes for a feature request, please add it Atlassian.

            Created 16/Jan/2020.

            I think I just follow issues like this out of morbid curiosity.

            We've got fields you can edit on the backlog now 🙄 … but we still can't see subtasks in the timeline.

            David Holman added a comment - Created 16/Jan/2020. I think I just follow issues like this out of morbid curiosity. We've got fields you can edit on the backlog now 🙄 … but we still can't see subtasks in the timeline.

            Having the 3 layer hierarchy on the timeline will be so helpful.  Yes we can access subtasks through other means but the timeline view enables us to inspect the same data in a visual way.

            Kevin Cressy added a comment - Having the 3 layer hierarchy on the timeline will be so helpful.  Yes we can access subtasks through other means but the timeline view enables us to inspect the same data in a visual way.

            We use Epics, Stories, Tasks, and Sub-Tasks to describe our work, using the hierarchy to help with both accountability and reporting. While we can manually tally the overall start and end dates for a story, it seems unnecessary to do that outside of the tool when we've articulated the work as sub-tasks to a story that could easily be displayed providing a valuable visual of the work. I'm working on a single story with 58 sub-tasks that spread over the next four weeks – it seems a shame to lose all that fidelity because the tool doesn't support something that is often requested and seems trivial to implement. 

            John Snuggs added a comment - We use Epics, Stories, Tasks, and Sub-Tasks to describe our work, using the hierarchy to help with both accountability and reporting. While we can manually tally the overall start and end dates for a story, it seems unnecessary to do that outside of the tool when we've articulated the work as sub-tasks to a story that could easily be displayed providing a valuable visual of the work. I'm working on a single story with 58 sub-tasks that spread over the next four weeks – it seems a shame to lose all that fidelity because the tool doesn't support something that is often requested and seems trivial to implement. 

            Paige Law added a comment -

            Currently building a plan with multiple dependencies, even on the subtask level! Would love to be able to see all the task dependencies

            Paige Law added a comment - Currently building a plan with multiple dependencies, even on the subtask level! Would love to be able to see all the task dependencies

            Stephan Grubbe Sølby added a comment - - edited

            The Timeline function in standard Jira is virtually useless without access to all three tiers in the standard plan. I can understand that not all would use this feature, but to restrict it's use, I simply don't understand.

            Likewise, the requirement to use epics and not just stories (or other standard issue types) is completely beyond me? Why make this decision for me? There are numerous free simple Gantt systems out there, why push your customers into the arms of the competition? It's not like I'm asking for premium planning features, but a simple Gantt function is not such a requirement. 

            Pretty please with sugar on top: Provide us with a useable timeline function.

            Stephan Grubbe Sølby added a comment - - edited The Timeline function in standard Jira is virtually useless without access to all three tiers in the standard plan. I can understand that not all would use this feature, but to restrict it's use, I simply don't understand. Likewise, the requirement to use epics and not just stories (or other standard issue types) is completely beyond me? Why make this decision for me? There are numerous free simple Gantt systems out there, why push your customers into the arms of the competition? It's not like I'm asking for premium planning features, but a simple Gantt function is not such a requirement.  Pretty please with sugar on top: Provide us with a useable timeline function.

            I'd love to have this feature, currently I have an awkward workaround.

            I want my senior leadership team and product manager to be able to look at the epics we're working on, and be able to drill into those to just see user stories, but no more, they don't care about the low level details we have in the tasks we do.

            It would be great if I could use subtasks to each user story to achieve this, but subtasks would render this impossible to see the timeline of tasks, to organise our work at a low level.

            So instead, I create tasks, manually link them to stories using "related to" link, and use the filters at the top of the board to filter for just user stories (for SLT/PM), and quick filters to see tasks belonging to a specific user story (for engineers).
            This is a lot of faff setting up appropriate board filters on an ongoing basis, when if I could just expand and collapse the user story in the same way epics expand and collapse, this would be a lot simpler and use the correct semantics of user stories having subtasks in order to complete them

            Mark McCracken added a comment - I'd love to have this feature, currently I have an awkward workaround. I want my senior leadership team and product manager to be able to look at the epics we're working on, and be able to drill into those to just see user stories, but no more, they don't care about the low level details we have in the tasks we do. It would be great if I could use subtasks to each user story to achieve this, but subtasks would render this impossible to see the timeline of tasks, to organise our work at a low level. So instead, I create tasks, manually link them to stories using "related to" link, and use the filters at the top of the board to filter for just user stories (for SLT/PM), and quick filters to see tasks belonging to a specific user story (for engineers). This is a lot of faff setting up appropriate board filters on an ongoing basis, when if I could just expand and collapse the user story in the same way epics expand and collapse, this would be a lot simpler and use the correct semantics of user stories having subtasks in order to complete them

            It's Christmas time, maybe Atlassian will look at their customer's whish list

            Eric Guichaoua added a comment - It's Christmas time, maybe Atlassian will look at their customer's whish list

            They probably couldn't drill down to the sub task to see this requirement, so they forgot

            John Hanzal added a comment - They probably couldn't drill down to the sub task to see this requirement, so they forgot

            This is critical. I also wish you could use the timeline view for projects set up with only stories and subtasks. Why does it only work for Epics and Stories? 

            Shane Grant added a comment - This is critical. I also wish you could use the timeline view for projects set up with only stories and subtasks. Why does it only work for Epics and Stories? 

            Jen Zane added a comment -

            This is an important necessary tool for project management reporting to executives.  This should not take a huge amount of development, as this worked in the past.  

            Jen Zane added a comment - This is an important necessary tool for project management reporting to executives.  This should not take a huge amount of development, as this worked in the past.  

            it's insane how much of a low hanging fruit this feature is! 

            Josh Ananaba added a comment - it's insane how much of a low hanging fruit this feature is! 

            Al Chen added a comment -

            I created a potential solution to this in Coda (disclosure: I work there). Coda acts as an extension of your Jira issues. After syncing in your Jira issues into a structured table in Coda, you can view them on a timeline layout where you can drill down into a parent issues' subtasks. Here's a short video showing this in action and the associated template.

            Al Chen added a comment - I created a potential solution to this in Coda ( disclosure: I work there ). Coda acts as an extension of your Jira issues. After syncing in your Jira issues into a structured table in Coda, you can view them on a timeline layout where you can drill down into a parent issues' subtasks. Here's a short video showing this in action and the associated template .

            Seems like it is visible in planer, but why dont you extent this to the timeline ? shouldnt be that difficult?

            Simon Schou Simonsen added a comment - Seems like it is visible in planer, but why dont you extent this to the timeline ? shouldnt be that difficult?

            This should be a basic feature.

            Talia Siegel added a comment - This should be a basic feature.

            For those who really need this feature, as this is not implemented in "basic" roadmaps, my suggestion would be to jump up to Premium plan tier which includes "advanced" roadmaps, or, you could use a third party addon like BigGantt or Structure.Gantt which are excellent alternatives. Obviously this means investment, but again, if you really need it, then you have choices.

            Javier Garay added a comment - For those who really need this feature, as this is not implemented in "basic" roadmaps, my suggestion would be to jump up to Premium plan tier which includes "advanced" roadmaps, or, you could use a third party addon like BigGantt or Structure.Gantt which are excellent alternatives. Obviously this means investment, but again, if you really need it, then you have choices.

            My team migrated away from Jira for project management alltogether because of the inability to have a clear overview of subtasks in the timeline. Is there any chance that this feature will at least be attampted to be implemented now that there is a new assignee or is this just a hot potato that gets thrown around and given to a person until the person leaves the company?

            Stefan Kubisa added a comment - My team migrated away from Jira for project management alltogether because of the inability to have a clear overview of subtasks in the timeline. Is there any chance that this feature will at least be attampted to be implemented now that there is a new assignee or is this just a hot potato that gets thrown around and given to a person until the person leaves the company?

            To be honest, I am pessimistic this feature will be released. 1000++ vote still not in progress. This feature is very important to us, without this the timeline is useless.

            Muhammad Dyas Yaskur added a comment - To be honest, I am pessimistic this feature will be released. 1000++ vote still not in progress. This feature is very important to us, without this the timeline is useless.

            Food for thought …

            I just finished merging a company that was on Jira Premium into a company that is not. They used Premium to get better a better view of plans because it was easier to upgrade an existing solution than license a better one under their previous owners.

            On the other side of the merger we were able to have a more comprehensive discussion about options. These little annoyances in Jira (and the generally poor integration between "Plans" and Jira proper) add up to enough that we had universal agreement that it's better to license Productboard for about the same money to get more features that are easier to use.

            Team Atlassian, it's time to get your act together. Your product just keeps getting more convoluted and unpleasant to use.

            David Holman added a comment - Food for thought … I just finished merging a company that was on Jira Premium into a company that is not. They used Premium to get better a better view of plans because it was easier to upgrade an existing solution than license a better one under their previous owners. On the other side of the merger we were able to have a more comprehensive discussion about options. These little annoyances in Jira (and the generally poor integration between "Plans" and Jira proper) add up to enough that we had universal agreement that it's better to license Productboard for about the same money to get more features that are easier to use. Team Atlassian, it's time to get your act together. Your product just keeps getting more convoluted and unpleasant to use.

            Hi - the requirement for sub-tasks to be visible in Timeline, is useful for stakeholders.  It allows the easy visibility of the tasks underpinning the overall Story/Epic and what state they are in and associated forecasted timeline.

            Without this, the real story and effort, is not able to be consumed by anyone visually through Timeline, others need to talk about the effort to stakeholders and communicate, which makes for a disjointed working process.

            Ultimately we want to share the info/data with others, so they can self-serve for consumption. 

            roy.dsouza@directlinegroup.co.uk added a comment - Hi - the requirement for sub-tasks to be visible in Timeline, is useful for stakeholders.  It allows the easy visibility of the tasks underpinning the overall Story/Epic and what state they are in and associated forecasted timeline. Without this, the real story and effort, is not able to be consumed by anyone visually through Timeline, others need to talk about the effort to stakeholders and communicate, which makes for a disjointed working process. Ultimately we want to share the info/data with others, so they can self-serve for consumption. 

            MJ added a comment -

            1000% Echo David DeTomaso!!!

            MJ added a comment - 1000% Echo David DeTomaso!!!

            This would be a very useful feature for us.  We need more granularity than just Epic/Task and it would be very helpful to view the start/end dates of sub-tasks in the timeline.

            David DeTomaso added a comment - This would be a very useful feature for us.  We need more granularity than just Epic/Task and it would be very helpful to view the start/end dates of sub-tasks in the timeline.

            vdhanorkar added a comment -

            Can we visible subtasks in timeline

            vdhanorkar added a comment - Can we visible subtasks in timeline

            So it would appear that Advanced Roadmaps and the Planning timeline function are separate products. The Premium subscription appears to provide the Planning product which gives everything that this Jira is about.

            As @Another Pissed Offson mentions, Atlassian get you in the details and scaling.

            But TBH, our costs moving from Jira Server to the Cloud went down sufficiently to fund the Premium service so ...

            YJ Rodrigues added a comment - So it would appear that Advanced Roadmaps and the Planning timeline function are separate products. The Premium subscription appears to provide the Planning product which gives everything that this Jira is about. As @Another Pissed Offson mentions, Atlassian get you in the details and scaling. But TBH, our costs moving from Jira Server to the Cloud went down sufficiently to fund the Premium service so ...

            Andrew Lee added a comment -

            Any update on this?

            Andrew Lee added a comment - Any update on this?

            Atlassian is a prominent software company known for its products like Jira, Confluence, Bitbucket, and Trello, which are widely used by businesses and organizations for project management, collaboration, and software development. While some people have concerns or criticisms about the company, it's essential to approach such discussions with fairness and objectivity.

            Critics of Atlassian often cite several reasons for their discontent, but it's important to note that there are also many satisfied customers who value the company's products and services. Let's explore some common criticisms while acknowledging the company's positive aspects.

            1. Pricing and Licensing Model: One frequent complaint about Atlassian is its pricing and licensing model. Some users find it expensive, especially as they scale up their teams or need more advanced features. Critics argue that the company could be more transparent and flexible in its pricing to accommodate a wider range of users.
            1. Complexity and Learning Curve: Atlassian's products can be complex, and some users find them challenging to set up and configure. The learning curve for tools like Jira and Confluence can be steep, leading to frustration for new users or smaller teams with limited resources.
            1. Product Integration: While Atlassian offers a suite of products, integrating them seamlessly can sometimes be challenging. Users may find it cumbersome to have multiple tools for different purposes and wish for more straightforward integration options.
            1. Customer Support: Critics have pointed out that Atlassian's customer support can be inconsistent. Some users report positive experiences, while others have faced difficulties in getting timely and effective support, particularly with more complex issues.
            1. Lack of Innovation: Some users feel that Atlassian's products have not kept up with the pace of innovation in the industry. They argue that the company should invest more in developing new features and improving the user experience.
            1. Limited Customization: While Atlassian's products are highly configurable, some users feel that they lack the level of customization they desire. They may want more flexibility to tailor the software to their specific needs.
            1. Competition and Monopoly Concerns: As Atlassian continues to acquire and expand its product offerings, some critics worry about its dominance in the market and the potential for stifling competition. They argue that a lack of competition can lead to complacency and reduced innovation.

            Another Pissed Offson added a comment - Atlassian is a prominent software company known for its products like Jira, Confluence, Bitbucket, and Trello, which are widely used by businesses and organizations for project management, collaboration, and software development. While some people have concerns or criticisms about the company, it's essential to approach such discussions with fairness and objectivity. Critics of Atlassian often cite several reasons for their discontent, but it's important to note that there are also many satisfied customers who value the company's products and services. Let's explore some common criticisms while acknowledging the company's positive aspects. Pricing and Licensing Model: One frequent complaint about Atlassian is its pricing and licensing model. Some users find it expensive, especially as they scale up their teams or need more advanced features. Critics argue that the company could be more transparent and flexible in its pricing to accommodate a wider range of users. Complexity and Learning Curve: Atlassian's products can be complex, and some users find them challenging to set up and configure. The learning curve for tools like Jira and Confluence can be steep, leading to frustration for new users or smaller teams with limited resources. Product Integration: While Atlassian offers a suite of products, integrating them seamlessly can sometimes be challenging. Users may find it cumbersome to have multiple tools for different purposes and wish for more straightforward integration options. Customer Support: Critics have pointed out that Atlassian's customer support can be inconsistent. Some users report positive experiences, while others have faced difficulties in getting timely and effective support, particularly with more complex issues. Lack of Innovation: Some users feel that Atlassian's products have not kept up with the pace of innovation in the industry. They argue that the company should invest more in developing new features and improving the user experience. Limited Customization: While Atlassian's products are highly configurable, some users feel that they lack the level of customization they desire. They may want more flexibility to tailor the software to their specific needs. Competition and Monopoly Concerns: As Atlassian continues to acquire and expand its product offerings, some critics worry about its dominance in the market and the potential for stifling competition. They argue that a lack of competition can lead to complacency and reduced innovation.

            I can confirm that Advanced Roadmaps, also known as Plans in Jira, is capable of displaying information down to the sub-task level. I have been using it for a long time.

            Javier Garay G added a comment - I can confirm that Advanced Roadmaps, also known as Plans in Jira, is capable of displaying information down to the sub-task level. I have been using it for a long time.

            988 votes puts this in the top 8 voted issues, and just 1 of those is In Progress. https://jira.atlassian.com/issues/?jql=project%20%3D%20JSWCLOUD%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20votes%20DESC%2C%20priority%20DESC%2C%20updated%20DESC

            I would say that probably subtasks first need to be able to be able appear on the backlog, but after that this should be the priority. We also use Advanced Roadmaps but having to create a plan there and switch to it to see the progress with subtasks is not ideal.

            Steven Rhodes added a comment - 988 votes puts this in the top 8 voted issues, and just 1 of those is In Progress. https://jira.atlassian.com/issues/?jql=project%20%3D%20JSWCLOUD%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20votes%20DESC%2C%20priority%20DESC%2C%20updated%20DESC I would say that probably subtasks first need to be able to be able appear on the backlog, but after that this should be the priority. We also use Advanced Roadmaps but having to create a plan there and switch to it to see the progress with subtasks is not ideal.

            Nikki DuBois added a comment - - edited

            Advanced roadmaps allows you to see sub-tasks HOWEVER the timeline (which used to be roadmaps) within the Jira project does not show you sub-tasks. Only Epics + Story/Task/Bug.

            I would like to have the option to see sub-tasks within the timeline view for each Jira project outside of the advanced roadmaps so teams do not have to leave their project to view the additional roadmap in plans.

            Nikki DuBois added a comment - - edited Advanced roadmaps allows you to see sub-tasks HOWEVER the timeline (which used to be roadmaps) within the Jira project does not show you sub-tasks. Only Epics + Story/Task/Bug. I would like to have the option to see sub-tasks within the timeline view for each Jira project outside of the advanced roadmaps so teams do not have to leave their project to view the additional roadmap in plans.

            @ fbff95e600cc , we are on Advanced Roadmaps, but the best Atlassian has been able to give us so far is

            Subtasks in the Timeline with Advanced Roadmaps ? (atlassian.com)

            which is essentially to convert sub-tasks into tasks

            YJ Rodrigues added a comment - @ fbff95e600cc , we are on Advanced Roadmaps, but the best Atlassian has been able to give us so far is Subtasks in the Timeline with Advanced Roadmaps ? (atlassian.com) which is essentially to convert sub-tasks into tasks

            Yes, we are on Premium Software, Standard Service.

            Allie Stewart added a comment - Yes, we are on Premium Software, Standard Service.

            I haven't seen it with my own eyes, but there are a few references to it that I've come across. 

            You can see an image on Atlassian's overview of Advanced Roadmaps at https://www.atlassian.com/software/jira/guides/advanced-roadmaps/overview#what-are-scenarios-in-advanced-roadmaps (about 3/4 down the page). 

            They also have this help topic about how to display subtasks on Advanced Roadmaps. https://confluence.atlassian.com/jirakb/how-to-display-subtasks-in-an-advanced-roadmaps-plan-1103431441.html

            And this one that again doesn't show it but shows how to set it up. https://community.atlassian.com/t5/Jira-Software-questions/How-to-display-sub-tasks-in-Advanced-Roadmap-view/qaq-p/1929196

            Others from non-Atlassian sources on Google as well. 

            Maybe it'll get pushed to standard users eventually...

            Sid Bergstresser added a comment - I haven't seen it with my own eyes, but there are a few references to it that I've come across.  You can see an image on Atlassian's overview of Advanced Roadmaps at https://www.atlassian.com/software/jira/guides/advanced-roadmaps/overview#what-are-scenarios-in-advanced-roadmaps (about 3/4 down the page).  They also have this help topic about how to display subtasks on Advanced Roadmaps. https://confluence.atlassian.com/jirakb/how-to-display-subtasks-in-an-advanced-roadmaps-plan-1103431441.html And this one that again doesn't show it but shows how to set it up. https://community.atlassian.com/t5/Jira-Software-questions/How-to-display-sub-tasks-in-Advanced-Roadmap-view/qaq-p/1929196 Others from non-Atlassian sources on Google as well.  Maybe it'll get pushed to standard users eventually...

            Joe Ancona added a comment - - edited

            @fbff95e600cc If that's the case, why the heck wouldn't Atlassian just come here to shut us down and reply saying that the Premium Plan contains the ability to view subtasks on the timeline? Sounds like a missed opportunity for them to push the premium plan onto an audience who's been screaming loudly for over a year for this very feature. Not saying you are incorrect on your theory, but it would seem like we'd already know. Plus, it goes against the statement they made above in August 2022... I think it's time for another update from @Rathesh Richards in my book.

            Joe Ancona added a comment - - edited @ fbff95e600cc If that's the case, why the heck wouldn't Atlassian just come here to shut us down and reply saying that the Premium Plan contains the ability to view subtasks on the timeline? Sounds like a missed opportunity for them to push the premium plan onto an audience who's been screaming loudly for over a year for this very feature. Not saying you are incorrect on your theory, but it would seem like we'd already know. Plus, it goes against the statement they made above in August 2022... I think it's time for another update from @ Rathesh Richards in my book.

            Is your team on the Premium plan? It has Advanced Roadmaps which appears to have this functionality. That would explain why Atlassian isn't eager to roll out this feature; they'd like their customers to pony up twice as much money monthly.

            Sid Bergstresser added a comment - Is your team on the Premium plan? It has Advanced Roadmaps which appears to have this functionality. That would explain why Atlassian isn't eager to roll out this feature; they'd like their customers to pony up twice as much money monthly.

            Yes, I can see Epic > Task > SubTask in my Timeline view.  On Cloud version.  I wish I could upload a photo of what I'm seeing but when I click Attachment, nothing happens.  Feel free to reach out to me directly if you wish and I can show you.  allie.stewart@lauramac.com 

            Allie Stewart added a comment - Yes, I can see Epic > Task > SubTask in my Timeline view.  On Cloud version.  I wish I could upload a photo of what I'm seeing but when I click Attachment, nothing happens.  Feel free to reach out to me directly if you wish and I can show you.   allie.stewart@lauramac.com  

            YJ Rodrigues added a comment - - edited

            @Allie Stewart, so in your Timeline view, you can see Epic, the Tasks under the Epics, and the Sub-tasks under the Tasks ?...

            I can only see Epics and Tasks... I find it time-consuming to have to open up a new pane or window to see the sub-tasks under a task, and manage them.

            YJ Rodrigues added a comment - - edited @ Allie Stewart , so in your Timeline view, you can see Epic, the Tasks under the Epics, and the Sub-tasks under the Tasks ?... I can only see Epics and Tasks... I find it time-consuming to have to open up a new pane or window to see the sub-tasks under a task, and manage them.

            What am I missing?  I can see and schedule my sub-tasks in the Plan.  Using Filter for Epic to Subtask.

             

             

            Allie Stewart added a comment - What am I missing?  I can see and schedule my sub-tasks in the Plan.  Using Filter for Epic to Subtask.    

            MJ added a comment -

            It would be phenomenal to see the subtasks show up on the gantt chart- game changer!

            MJ added a comment - It would be phenomenal to see the subtasks show up on the gantt chart- game changer!

            Please add this, very important and really distracts from the whole planning/Jira quality. 

            Alissa Balfoort added a comment - Please add this, very important and really distracts from the whole planning/Jira quality. 

            muyiwa added a comment -

            You have an awesome product in JiraSoftware cloud. I'm a new user preparing to onboard a small team with Jira and I'm quite sure visibility of subtasks in timeline and backlog would have an outsized impact on the quality of dialog in our team syncs. It would also justify the amount of time I'm putting trying to deliver complete project configurations (I want folks to readily see from the project to the sub-task details).

            Thanks for all the work you are doing. Hope you make this feature live on the Standard plan soon. Cheers

            muyiwa added a comment - You have an awesome product in JiraSoftware cloud. I'm a new user preparing to onboard a small team with Jira and I'm quite sure visibility of subtasks in timeline and backlog would have an outsized impact on the quality of dialog in our team syncs. It would also justify the amount of time I'm putting trying to deliver complete project configurations (I want folks to readily see from the project to the sub-task details). Thanks for all the work you are doing. Hope you make this feature live on the Standard plan soon. Cheers

            We would like to see this functionality for following reasons:

            • We have quite some subtasks (20 to 30) under specific User Stories and hence would like to be able to
              • drill down to the subtask-level to see what is in the User Story
              • see flow and inter-dependencies between these subtasks

            Danny Willen added a comment - We would like to see this functionality for following reasons: We have quite some subtasks (20 to 30) under specific User Stories and hence would like to be able to drill down to the subtask-level to see what is in the User Story see flow and inter-dependencies between these subtasks

            Timeline is the perfect place to show an integrated view of a roadmap execution. Large stories (that cant be split) tend to have a lot of subtasks and those subtasks in turn tend to blaock other tasks or stories. 

            This new In depth view will allow for complex roadmaps to be handled in a more effective way.

            Hugo Guimarães Soares added a comment - Timeline is the perfect place to show an integrated view of a roadmap execution. Large stories (that cant be split) tend to have a lot of subtasks and those subtasks in turn tend to blaock other tasks or stories.  This new In depth view will allow for complex roadmaps to be handled in a more effective way.

            Wir brauchen diese Funktion unbedingt!

            Markus Mettmann added a comment - Wir brauchen diese Funktion unbedingt!

            please enable this, should be fairly simple

            Britta Rinke added a comment - please enable this, should be fairly simple

              bb3b5f443b59 Amy Cheong
              emccutcheon Earl McCutcheon
              Votes:
              1689 Vote for this issue
              Watchers:
              710 Start watching this issue

                Created:
                Updated: