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,559,603
Community Members
 
Community Events
185
Community Groups

How to setup project and repositories?

Patricia Campos
Patricia Campos Feb 18, 2021

Hi!

We have a number of different applications and version that our development team supports, something like below.

 

Website ver 1 support by Team A

Website ver 2 supported by Team A

Billing ver 1 supported by Team A

Billing ver 3 supported by Team A

EDI ver 4 supported by Team C

Config file supported by Team D

We created a workspace where teams A B C and D can keep their files. I'm just not sure how we are supposed to setup the Projects and Repositories. Can anyone point us to the right direction?

 

Comment
Watch
Like Be the first to like this
310 views

1 comment

Tyler T
Tyler T
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 19, 2021

It seems like you could use a single workspace for the entire team and each project could be a project (website, billing, edi) etc. And then within each project you could have an individual repository for the versions; unless those can be in different branches. If the versions of each website share code, then it might make more sense to have branches for the various versions of the projects, unless there isn't a version considered the main version.

Does that help?

Like
Reply

Comment

Log in or Sign up to comment
Bitbucket
Bitbucket
TAGS
AUG Leaders

Atlassian Community Events

See all events