Tempo Ideas

Welcome to Tempo’s Idea Portal! Your suggestions are valuable to us and help us make our products even better.
Below is a list of ideas for Tempo, so please search, review and vote for those that would help you the most. We encourage you to add an idea if you don’t see it listed. You can stay updated on the work we are doing here at Tempo by contributing to this page.
To learn more and see our Frequently Asked Questions, click here.

Create groups from Epics

A lot of backlogs and work is already grouped in Jira through the use of epics. It would be great to automatically create and manage groups based on epics in the scope.

  • Ingi Brown
  • Oct 31 2019
  • Shipped
Tempo Products Cost Tracker for Tempo Timesheets
Tempo Platform Cloud
  • Attach files
  • Admin
    Christopher Castine commented
    24 Feb 06:25pm

    Hi Jonas,

    Thanks for sharing. This is something we are aware of and this limitation is noted in the help documentation. Unfortunately, as you mentioned, this is due to a Jira technical limitation. Additional development will be required on our side to address this. We do not have delivery date at this time but will update the Cost Tracker community when we have further information.


    Best Regards,

    Christopher Castine

    Director of Product Management

  • Jonas Boernicke commented
    24 Feb 10:29am

    Hey Christopher,

    One thing I just realized when trying to use the new feature, all the sub-tasks are not being added to the Epic groups. Yes, they cannot be linked to an Epic directly but they really should be grouped into their parent's Epic. Are you aware of this little bug?


    Cheers

    Jonas

  • Jonas Boernicke commented
    24 Feb 09:09am

    Oh my god, thank you so much! This actually makes Cost Tracker usable again for our workflow and analyses!! Awesome that you are listening to user feedback in that way. 👍🏼

  • Admin
    Christopher Castine commented
    23 Feb 08:34pm

    HI All, just a quick note to let you know that this feature is shipped and now available for use.


    Cheers!


    Christopher Castine

    Director of Product Management

  • Admin
    Christopher Castine commented
    22 Jan 01:13pm

    Hi Jonas,


    Thanks for reaching out. I am doing great and I hope you are as well. I use Cost Tracker internally at Tempo, so I fully understand the amount of manual work required at this time. Good news, the team has started working on this and I expect it to be in production late February.


    Best Regards,

    Christopher Castine

    Director of Product Management

  • Jonas Boernicke commented
    21 Jan 08:36am

    Hey Christopher,

    Hope you guys are doing fine. Any news on this feature? The multi-select feature is nice, but sorting 200+ tickets into Epics manually is tedious and we end up not using Cost Tracker as much due to it. It feels like an essential feature, otherwise the "Scope" tab is not very helpful for us.

    Cheers and stay healthy

    Jonas

  • Luke Bowler commented
    22 Oct, 2020 11:23pm

    I agree with this and would also like the option to group by Component. By way of example, in an agency context, I have many group marketing clients who have a single BAU retainer to service the needs of multiple business units. Not wanting to bastardise Epics, we’ll use Components to enable us to report back on how the budget is being apportioned by business area.

  • Admin
    Christopher Castine commented
    2 Sep, 2020 12:12am

    Hi Andrew, Hope you are doing well. Please see my answers below. Nothing planned for the immediate, as there is some key functionality that is taking precedence. We can revisit these late 2020 / early 2021.

    a) This is something I would like to see improved in the product as well. However, there are some technical challenges around this and the implementation is not that straight forward. We have no immediate plan now but it is something that we will consider in the future.

    b) Something we could consider in the future but further technical assessment will be required.

    Best Regards,

    Christopher Castine

  • Andrew Stewart commented
    13 Aug, 2020 05:11am

    Thank for you the update Christopher, though can I clarify:

    a) I don't see Epic as a Column, it does appear next to the Issue Reference but isn't showing as a column. Are there any plans to make this a field we can sort on?

    b) We make quite extensive use of sub-tasks - given these Issues do not have an Epic Link of their own it is not possible to easily identify which group these should be dragged under. Your proposed workaround doesn't seem to help for these.

  • Admin
    Christopher Castine commented
    10 Aug, 2020 07:27pm

    The scope tab now supports the Epic column. We also support a right click with a multi select with move-to or create group, that should greatly speed up this process. Based on this, a fully automated approach is deferred for now.

    Regards,

    Christopher Castine

    Cost Tracker Product Manager

  • Andrew Stewart commented
    12 Jun, 2020 05:41am

    Since the Roadmaps feature in Jira, which will be available to all users shortly, encourages users to use EPICS to represent main activities there are going to be an influx of people wanting to run cost reports by Epic.

    The current design that requires us to manually create groups, and then manually assign tickets, only works for projects with a very very small number of tickets. We have projects with several dozen tickets, sometimes hundreds, which means that manual grouping is not feasible.

  • Guest commented
    14 Feb, 2020 01:27pm

    This feature seems to be absolutely necessary !

    Can't wait to test it !

  • Malvina Garnier commented
    12 Feb, 2020 05:17pm

    This would be awesome !!!

  • Mike Kondrashin commented
    18 Dec, 2019 03:33pm

    This would be a massive improvement!

  • Guest commented
    3 Dec, 2019 11:46pm

    This would save us soooo much time. Total time spent across tasks in an epic is an oddly difficult number to pull out of Jira. I'm currently mirroring my groupings with epics but this is a lot of manual time and prone to errors if someone moves something out of an epic. This would improve the usage significantly.

     

    Automatic groupings by epic would help our org out a lot but I could see auto-groupings by many other types like story/sub-task, component, version, labels.

  • Guest commented
    20 Nov, 2019 05:55pm

    Epics to issues and also to sub-tasks would be perfect

  • +1