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.
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.
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.
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.
This is really important for us! Different business lines have different metrics and reporting needs.
Attachments Open full size
Attachments Open full size
This is really a massive showstopper for us! Please urgently think of a solution to add attributes per project.
Attachments Open full size
Hello,
I need this improvment too.
Still just an idea ?
Regards.
Amy-
Attachments Open full size
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?
Attachments Open full size
We need this feature as well to keep the Log Screen clean of irrelevant fields for different kinds of projects.
Attachments Open full size
Pls make it happen.
Attachments Open full size
Showstopper if not available.
Attachments Open full size
Please make it happen... :(
Attachments Open full size
Is this still just an idea?
Attachments Open full size
We too need this feature.
Attachments Open full size
We need this feature, we also have over 1k projects and 8k users. We need to set the work attributes per project.
Attachments Open full size
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!
Attachments Open full size
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.
Attachments Open full size
I'm updating this to future consideration.
Attachments Open full size
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.
Attachments Open full size
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.
Attachments Open full size
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
Attachments Open full size
Hi,
This should also include the possibility to make work attributes mandatory or not depending on the project / issuetype for instance.
Vincent
Attachments Open full size