You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I used to work primarily in GitHub/BitBucket Issues for our project management. We moved into Jira about 8 months ago, and I like it a lot, but there's still one thing I'm a little confused about.
In GitHub/BitBucket, the nice thing is that we have a public repo where everybody can see what issues are in the backlog, and they can create their own issues to add to that backlog if they want to.
This also allows them to see what work there is to get done, so if they want, they can contribute to the open source project and help us complete the work.
Now that we have all of our stuff moved into Jira, our GitHub/BitBucket repos looks kinda dead. There are no more issues there, no more comments and action going on within our public repo there.
I feel like this was a step backwards in that regard. We're still using GitHub/BitBucket for our projects in general, but I feel like I'm missing out on that public aspect now that it's all hidden behind Jira.
Am I missing something obvious? Any information on this would be greatly appreciated.
Thanks for the feedback. These seem like interesting options. Unfortunately, they each seem to come with quite a bit of additional overhead.
Yes, previously, I simply used BB/GH as the project management system. We created "issues" there exactly like we create "tickets" in Jira.
Then the dev team worked directly from that issue. All of the commits, pull requests, etc. happened right there, just like they still do now except it's all hooked up to Jira so we can see the commits/branches.
So when we moved to Jira, we exported all of the issues out of BB/GH and imported them into Jira. Then closed all of those issues at BB/GH. So again, now those public repos look sort of dead. I mean, you can still see that commits are happening on a regular basis, but you can't a backlog anymore.
I'll consider some of your options above and see if I can figure something out. Thanks again for the feedback.
Do all projects need to be public or can we just select the ones related to our open source product and make those public.
I have internal teams using it for internal tasks that i want to keep private
Also this is only supported for basic , what happens if we were to migrate to premium?