If you add the Tempo Team custom field to a JIRA issue, this immediately blocks users from seeing the issue in the filter results unless they have browse access to the team.
At this level, the filters should be open to whoever the filter is shared with and whoever has browse access to the repository. With adding Tempo Teams to the form, it now adds an additional layer that the user must have browse access to the Tempo Team and its members timesheet.
Note: If I search for the issue individually, I can view the filter results. If I include "Tempo Team = ABC" in my JQL query, the timesheet permissions kick in.
Has anyone ran into this issue? I figured I would ask the community before submitting to Tempo.
So, from your comments I began to open a support ticket. I wanted to retest and provide good steps and low and behold it doesn't happen happen anymore.
I'll keep playing around and if it does occur, I'll try to record it and open a support issue.
FYI - This was with JIRA 6.1 and Tempo 7.8.2.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs