Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
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

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,458,298
Community Members
 
Community Events
176
Community Groups

One "Project" or Many with bit bucket integration

Jim Lile
Jim Lile Jan 23, 2018

When setting up our backlog what are the pro's and con's of multiple Projects in jira? We have bitbucket and Jenkins and we want to fully integrate the capability for tracibility and versioning. Our team of architects believes separate Projects by Products is cleanest but I'm concerned about having multiple Projects because often times when we release, we push out 2 to 3 Products into one release. I believe having 4 Projects (for our 4 products) requires the PO to write stories in different backlogs. Thoughts? 

Comment
Watch
Like Be the first to like this
433 views

1 comment

Jobin Kuruvilla [Adaptavist]
Jobin Kuruvilla [Adaptavist] Rising Star Jan 23, 2018

You will have to write different stories but doesn't it make sense because they are for different products?

And having stories in different projects doesn't mean they cannot go into the same backlog. You can have a single board for all those projects if it is the same scrum team that is working on it. Boards belong to the teams, not to the project.

There is no disadvantage in terms of the integration as well. In the end, it depends on your process because JIRA can handle both approaches.

Like
Reply

Comment

Log in or Sign up to comment
Bitbucket
Bitbucket
TAGS

Atlassian Community Events

See all events