Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Does anyone else use Tempo with Portfolio

We are using Tempo Timesheets and Tempo Budgets.

 

We are just starting to look at Portfolio but need some recommendations.

 

We have JIRA projects setup for each Agile development team and tech services team.  We do not create JIRA projects for each IT project, instead we create a Tempo account to tie all of our JIRA across teams/JIRA Project.

 

Portfolio looks like it ties very nicely with JIRA Project but I want to create a JQL to go across tempo account each as "Account in (PRJ18FMS)  ORDER BY created ASC"

 

I have been told that filter is not the best way to create a project due to possible performance issue.

 

Is this true?

 

What recommendation due you have to create a Portfolio project that contains work from multiple teams.

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events