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.

Allow all tickets within an Epic to inherit the Epic's Account

Tempo would be much more valuable if we could allow tickets within an Epic to inherit the Account of the Epic.

The problem with not having this functionality is that every single ticket needs someone to select this field and we will end up missing things. We have thousands of tickets. If we miss tickets then our CapEx/OpEx reporting will be inaccurate. We also cannot expect that individual user's will know which account to select when submitting their time log.

  • Guest
  • Jun 30 2020
  • Future consideration
Tempo Products Tempo Timesheets, Tempo Planner
Tempo Platform Cloud
  • Attach files
  • Gerhard Mesch commented
    30 Aug 09:01am

    Hi everyone, this feature would be extremely helpful for us on our Data-Center instance. Currently it is also pretty confusing to train members with the current state because:

    1. It is working for Issue -> Sub-Issue

    2. It is working the Teams field correctly.

  • Hlynur Johnsen commented
    26 Feb 01:13pm

    Hi everyone,

    As pointed out in the previous comment, it's possible to solve this use case with Automation for Jira, although that solution might not be viable for everyone. For those with Jira Cloud Premium or limited usage, an Automation for Jira rule like the one documented here can work for you.

    At the moment we do not have an exact ETA for this being built into the product.

    Regards,

    Hlynur Johnsen

    Group Product Manager

  • Nicholas Tsiroyiannis commented
    28 Jan 10:02pm

    Yes I agree, this is critical for us too as we currently need to use automation which will breach our automation limits in jira