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.

Different work attributes by projects

Being able to create different Work Attributes for different projects or team.

  • Ingi Brown
  • Jul 15 2019
  • Future consideration
Tempo Products Tempo Timesheets
Tempo Platform Cloud, On-Premise
  • Attach files
  • Rahul A commented
    27 Apr 04:14pm

    We too need this feature.

  • Guest commented
    6 Apr 10:04am

    We need this feature, we also have over 1k projects and 8k users. We need to set the work attributes per project.

  • Valeria commented
    6 Apr 09:48am

    Highly requested feature! Our Jira instance runs more than 1000 different projects and having common Work Attributes is not an option. Please consider adding flexibility to set Work Attributes on a project level. Thank you!

  • Joao Antunes commented
    31 Aug, 2020 11:12am

    This flexibility is quite important if you start using JIRA/Tempo to track different scopes of work (e.g. Professional Services vs Product Development) where even if you share some attributes, the values available will probably need to be different.

    There could also be a quick win here, where for each attribute we could say if it should appear when logging time for internal issues. Thank you.

  • Hlynur Johnsen commented
    30 Jul, 2020 10:54am

    I'm updating this to future consideration.

  • Oleksandr Chalyi commented
    21 Jul, 2020 02:37pm

    Hi,

    Our jira instance includes over 400 projects.

    Projects requesting new work attributes we have to reject since we already have a long list of values available to all users. Adding more values will make search in Work Attributes inconvenient.

    Wondering how other users workaround this.

  • Patrick Jörg commented
    16 Jul, 2020 01:10pm

    I have been told, that this is also a feature we need. Our use is this, we have a like "static" project to log holidays and alike. In this project there are different accounts. The users don't have the permission to change the issues in that project, so they can't change the account. However when logging time the account is mandatory and can be choosen. It doesn't have an effect on the actually logged account, but its confusing.

  • Hlynur Johnsen commented
    3 Apr, 2020 10:18am

    Hi Vincent,

    Thanks for the feedback. This is something we have been considering in the past, and we are definitely interested offering features like this in the future. That said, I don't see this being prioritised this year unless it gathers more momentum in the votes. Therefore I'm putting it in Unlikely to implement for now - but we'll keep a close eye on this one going forward.

    Cheers,

    Hlynur Johnsen

    Group Product Manager - Tempo for Jira

  • Guest commented
    19 Mar, 2020 08:35am

    Hi,

    This should also include the possibility to make work attributes mandatory or not depending on the project / issuetype for instance.

    Vincent