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.
To be able to differ between different work logging configurations in an enterprise with different teams is a must-have. Having only one configuration is an annoying compromise for every team using the one and same dialoge.
It's extremely inconvenient for our organization to have to scroll down through a long list of work attributes every time we log time. Sounds like we have a similar setup with @Isabel Aguilar, where each one of our teams have certain attributes that apply to some projects and do not apply to others. We have over a dozen of teams.
This is crucial for our setup as we have projects for different areas and some of them need work attributes as mandatory and other areas not. This was created in 2020, is not any option to develop it?
This is a showstopper for our tempo adoption. Different projects, in different countries, absolutely need localized and specific list of values for each attribute (mostly to speficy things like standard time, overtime, work from home, etc)
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!
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.
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.
Ingi Brown
Not having this makes it difficult to have mandatory attributes. We have teams that need them and others that do not.
To be able to differ between different work logging configurations in an enterprise with different teams is a must-have. Having only one configuration is an annoying compromise for every team using the one and same dialoge.
It's extremely inconvenient for our organization to have to scroll down through a long list of work attributes every time we log time. Sounds like we have a similar setup with @Isabel Aguilar, where each one of our teams have certain attributes that apply to some projects and do not apply to others. We have over a dozen of teams.
This is crucial for our setup as we have projects for different areas and some of them need work attributes as mandatory and other areas not. This was created in 2020, is not any option to develop it?
This is really important for us! Different business lines have different metrics and reporting needs.
This is really a massive showstopper for us! Please urgently think of a solution to add attributes per project.
Hello,
I need this improvment too.
Still just an idea ?
Regards.
Amy-
This is a showstopper for our tempo adoption. Different projects, in different countries, absolutely need localized and specific list of values for each attribute
(mostly to speficy things like standard time, overtime, work from home, etc)
Is this planned for an upcoming release?
We need this feature as well to keep the Log Screen clean of irrelevant fields for different kinds of projects.
Pls make it happen.
Showstopper if not available.
Please make it happen... :(
Is this still just an idea?
We too need this feature.
We need this feature, we also have over 1k projects and 8k users. We need to set the work attributes per project.
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!
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.
I'm updating this to future consideration.
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.