JIRA OnDemand and Tempo

[Joe Murray]

Due to the difficulties with preventing client users from seeing projects relating to other clients, we have tended to not expose our main JIRA OnDemand project to them. For the few projects where we really need to be assigning tickets to users in the client organization, we set up separate JIRA OnDemand instances.

While our preference is to have Atlassian better support Consulting shops with multiple clients in OnDemand, they have indicated via support tickets that this is not a priority for them. This causes us to need to aggregate time tracking and resource allocation across JIRA OnDemand instances, which is mostly a manual process. Does Tempo support integrating information from more than one instance of JIRA, and specifically, more than one OnDemand instance?

[MJ · Accepted solution]

Hi Joe,
It is not possible to use Tempo in the way as you described in your question. It is however possible to shield off projects from certain users by making good use of permission schemes, project roles and groups. I think by using multiple OnDemand instances you have been overcomplicating things for yourself, while you can build such a configuration within 1 and the same instance. If you require additional assistance on this, please contact us.

[Viðar Svansson [Tempo]]

I think the main problem here is that he can't give clients access to the tickets where timetracking is performed because JIRA makes it impossible to shield timetracking data using the permission configuration features.

He can however how two separate tickets that are linked in the same instance, on for the client and one for internal work.