Portfolio conflict with Tempo timesheets

[Julian McEwen]

We're using Tempo time sheets and also need to use Jira Portfolio (cloud).

Portfolio requires the 'Time tracking provider' be set to 'Jira provides time tracking'

Tempo automatically sets (and needs) the 'Time tracking provider' to 'Tempo Timesheets'

Portfolio can't update issues when Tempo time tracking is enabled.

Does anyone know of a solution or work around to this? Or is it simply not going to work. (also not interested in using Tempo planner instead of portfolio as it doesn't quite fit our needs)

[Ioannis Iliadis]

Any updates on this ? 

We can understand that this is a conflicting issue between parts BUT its critical for companies who use both solutions .

[Marcin Gebski]

Hi, I've stubled upon this as well.

Does anybody know when this issue started occuring? What was the last pair of versions that were working together?

[Julian McEwen]

I've more or less given up on Portfolio because of this. The dev team needs Tempo and this doesn't seem to be a priority for Tempo or Portfolio.

[Marcin Gebski]

But is there any reasonable alternative to Portfolio around? I mean, for visualisation of roadmaps based on backlogs, considering epics and versions?

[Julian McEwen]

tbh, portfolio seems like the best solution to me outside of more expensive solutions like Aha! (+jira integration) ( www.aha.io )

I'm not sure how it handles backlogs, epics and versions but it looks pretty capable.