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 add more details to this, the flex plan is driven by teams. Even though it takes into account the assigned plans to the resources in the team(s) to give you an idea of current allocation vs newly planned time. Once you create the flex plan(s) and then associate them to a jira issue. If anyone were to use the resource planning view, they would not know that other plans have been assigned to the team because it is not assigned to any resources on the team. We're unable to convert and assign to a resource or resource(s) later.
We also use Structure, so we use the Tempo planner field to get the planned time, the flex plan time only goes to original estimate, it does not go to tempo planner field. It feels short sighted at that point.
Jeba Priyanka
to add more details to this, the flex plan is driven by teams. Even though it takes into account the assigned plans to the resources in the team(s) to give you an idea of current allocation vs newly planned time. Once you create the flex plan(s) and then associate them to a jira issue. If anyone were to use the resource planning view, they would not know that other plans have been assigned to the team because it is not assigned to any resources on the team. We're unable to convert and assign to a resource or resource(s) later.
We also use Structure, so we use the Tempo planner field to get the planned time, the flex plan time only goes to original estimate, it does not go to tempo planner field. It feels short sighted at that point.