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.

Add the option that issues, which are added via filter to the My work view, comply to the grouping

Many users are using the option to add JIRA filters to their My work view, to easier find them when they log work.
The functionality to have these issues (when no work has been logged on them in the selected timeframe) comply to the grouping is scheduled to be removed, which will affect the users who are currently using this.
The display of the issues will then change continuously as users are logging work.

  • Susanne Barbara Götz
  • Feb 18 2021
Tempo Products Tempo Timesheets
Tempo Platform On-Premise
  • Attach files
  • Martin Leitner commented
    9 Jul 09:21am

    As of 7 July 2021 I could bring this feature back by the help of Tempo support and by performing a downgrade to Timesheets 11.2.2.

    Not that all Tempo System plugins and Timesheets plugin itself need to uninstalled first before Timesheets be manually uploaded in the local Jira server instance by providing the link for 11.2.2 under 'Download' from https://marketplace.atlassian.com/apps/6572/tempo-timesheets-time-tracking-reports/version-history.

  • JIRA Support commented
    17 Jun 02:34pm

    I agree with previous comments: this is a regression, but caused by strategy, and have to be reimplemented.


    It is something I have been scared about since the announcement to retire the Server license: Atlassian is pushing the Cloud version, which will be the master also for the Data Center, even if reducing features.

    In my opinion, within 3y Atlassian will announce to retire the Data Center as well


    Tempo, you should multiply our "votes" as JIRA admins because we are the voice of all our stakeholders; and please be more clear if you are going to deprecate other features


    Cristian


  • Michael Bachmann commented
    17 May 07:47pm

    This is a serious degradation of functionality that makes the use of the timesheet nearly impossible when working with lots of issues.

    All of our users rely heavily on filters and grouping them however a user needs it is crucial in keeping it somewhat manageable.

    This has worked perfectly fine up until now. Why was this not even announced? It is only listed as a "fix" in your changelog.

    I'm really lost on how we are supposed to continue working with these kinds of arbitrary limitations...

  • Caroline Vanmaele commented
    21 Apr 06:05pm

    We have been using this functionality since we started to use Tempo for timesheets. Most of our users populate their timesheet with a filter. And obviously you would like to group those issues according to the project as an absolute minimum. But it makes as well a lot of sense to group based on subtasks.

    Refreshing the view is already quite slow today. If the sequence of the issues is continuously changing because issues without hours logged are not considered in the grouping, the speed will only come down. And imagine the frustration of users whose issues are continuously moving around.

    This functionality was available before. So difficult to grasp why it is removed for new releases. It would be great if you can add this again.

  • Michael Mohr commented
    7 Apr 06:25am

    You are reducing the functionality of your on premise version to the one of your cloud version. So that the cloud version is no longer the one with reduced functionality , so that customers have no reason to choose on premise installation over cloud installations.

    The reason why we believe this, is because the filter and group by functionality worked fine for us till 11.20 without any problem for years. So the incompatibility that you are mentioning could only be caused by restrictions of your cloud version, not by technical or functional problems of your on premise version.

    Shame on you that you solve these incompatibilities by reducing the functionality of your on premise version to reduce your dev efforts to maintain both versions in a own dev trunk. But in parallel you have raised your subscription costs of Tempo from the server to the data center version dramatically in the last years/month. So that there should be enough money for own dev branches for bot versions.

    Formerly working with Jira Apps like Tempo was great, but meanwhile it seems so that the financial people at Atlassian and the App Vendors has won the battle, so that now only profit counts and no longer satisfied customers!