Portfolio conflict with Tempo timesheets

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)

3 answers

Any updates on this ? 

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

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?

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.

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

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.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Mar 13, 2019 in Marketplace Apps

Marketplace Spotlight: Marketing apps for Confluence to keep your teams working on the same page


214 views 0 6
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you