We would like to submit a feature request to make Multiple Membership Periods information visible to Team Leads.
In our Jira instance, the global permissions Tempo Administrators and Tempo Team Administrators are centrally managed by Jira Administrators, as we support multiple teams across different studios. Granting the Tempo Team Administrator role to selected Team Leads is not a viable option, as this permission includes the ability to delete teams and programs, which presents a significant risk.
Additionally, having support for multiple membership periods is very important for our customers. Team composition changes frequently - people join, leave, or temporarily move between teams - and maintaining a clear history of these membership periods is essential for accurate reporting, capacity planning, and auditing.
They also use Teams as a lightweight resource planning structure. It would be significantly easier and more transparent for Team Leads and team members to clearly see the exact periods during which someone is or was part of their team. This visibility helps with understanding past allocations, validating time tracking data, planning future capacity, and ensuring proper ownership of work during specific timeframes.
Without multiple membership periods being clearly visible to Team Leads, this information remains difficult to access and manage efficiently, creating unnecessary administrative overhead and reducing transparency.
Beatrice Avram
| Tempo Products | Tempo Teams, Tempo Timesheets |
| Tempo Platform | On-Premise |
Have there been any discussions or plans to address this limitation, either through a product enhancement or another solution that would allow multiple membership periods for the same user and team to be displayed in the UI?
This is an issue we are encountering quite frequently across our customer base. Since Tempo stores the historical membership periods correctly at the database level, it would be extremely helpful to have this information accessible in the UI as well.
At the moment, we need to work around this limitation by hardcoding additional logic into our reports to account for multiple assignments and reconstruct the actual membership history. This adds unnecessary complexity and ongoing maintenance effort.
Could you please let us know whether this functionality is on your roadmap, or if there are any plans to introduce a solution that would accommodate this use case?
It would be very valuable for us and our customers, particularly from reporting, transparency, and auditing perspectives.
Thanks in advance for your feedback!