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,558,371
Community Members
 
Community Events
184
Community Groups

Cloud JIRA Confluence Bitbucket integration

Edited

I'm using Bitbucket, JIRA and Confluence in the Cloud.

At the moment, I'm building up the representation of my customer projects  distributed over the three applications.

This mainly consists of migrating the former representation in svn, Trac and Confluence over to the new representation.

My question is now: What to use as a knowledge base around Bitbucket Repos?

Bitbucket offers its own Wiki as versioned Markdown files which is directly connected to the repo, but currently I'm building most of the customer documentation in Confluence.

Ideally, I would be able to use Confluence as a drop-in replacement for the Bitbucket Wiki, creating one space per repo, but this does not seem to be an option.

How do others handle this, or is there a canonical way? Should I live with two distinct Wiki technologies?

1 comment

Ana Retamal
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jan 11, 2018

 

Hi Stephan, that would really be a personal decision. Do you want this documentation to have the same appearance as the rest of the knowledge base you're building? or do you prefer the wiki to be associated per repo?

As there isn't just one "valid" answer, I'll move this post to the discussions section so other users can share their opinions and tips too.

Hope that helps!

Ana

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events