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 would be useful. We use the resource planning to account for PTO and leave, and the team planning view to see how work items (generally epics) fit into the team's capacity.
Being able to factor in generic resources would enable us to understand how staffing up or down a team could impact projects, and would enable us to create hypothetical team staffing scenarios to get an idea of how we could staff up new projects.
The integration of generic resources as team resources is necessary in order to be able to plan larger development projects iteratively and break them down successively. The intention is to be able to plan larger development projects in blocks, long before it is planned at a head level who is doing what and by when. Planning Jira tickets directly on Teams is not a substitute for this because no Tempo planning objects are created in this mode and Tempo-specific properties and workflows such as splitting into multiple planning objects are not supported. I therefore support this feature.
This would be useful. We use the resource planning to account for PTO and leave, and the team planning view to see how work items (generally epics) fit into the team's capacity.
Being able to factor in generic resources would enable us to understand how staffing up or down a team could impact projects, and would enable us to create hypothetical team staffing scenarios to get an idea of how we could staff up new projects.
The integration of generic resources as team resources is necessary in order to be able to plan larger development projects iteratively and break them down successively. The intention is to be able to plan larger development projects in blocks, long before it is planned at a head level who is doing what and by when. Planning Jira tickets directly on Teams is not a substitute for this because no Tempo planning objects are created in this mode and Tempo-specific properties and workflows such as splitting into multiple planning objects are not supported. I therefore support this feature.