We collaborate closely with external stakeholders who have access to selected Jira projects. To enable efficient communication and progress tracking, they need to view and contribute to issues. However, the current setup also exposes our time tracking data, which is internal and sensitive.
Unfortunately, Jira doesn’t support field-level security, meaning we can’t restrict visibility of specific fields like Timespent while still allowing issue access. Because of this limitation, I’m reaching out to Tempo to explore a better approach.
What we’d ideally like is the ability to fully disable Jira’s native time tracking and rely on Tempo exclusively for this functionality. That would allow us to control access to time tracking through Tempo’s own permissions, ensuring sensitive worklog data remains private while maintaining seamless collaboration for external users.
This would solve a significant real-world problem for teams that use Tempo across mixed internal–external environments and would make Tempo even more valuable as the central, secure layer for time management in Jira.
Guest
| Tempo Products | Tempo Timesheets |
| Tempo Platform | Cloud |
