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

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,414,280
Community Members
 
Community Events
170
Community Groups

JIra best practices for defining products and projects with Big Picture in mind

I just started in my company and used Jira previously. This org has acquired big picture as well and I'm trying to make them work together. Some things that concern me in the current set up are as follows:


1. Each jira project is really a product and a new board is defined for every project. So imagine product is say a mobile app, and every project for that app is a different board within the project. 

 

My thought is that with this setup Big Picture will not be able to work correctly. I was thinking that the product should be defined as a portfolio in Big Picture and then the projects in jira each have a single board.

 

If this is true then should I create a brand new instance and migrate projects across into the new (and proper) set up?

0 comments

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events