7 ms·

I like Bitbucket and have been using them for some time but their interface is slow and not as intuitive as Github's.

nevi-me 12y ago
Also like Bitbucket, and agree with the interface. They made things responsive a while ago, and there were lots of complaints about the 'create a README' decision as a space-waster, they haven't done anything about it since. I like their revenue model, but because of the existence of JIRA and Stash, Atlassian are refusing/reluctant to improve the issue tracker in Bitbucket. For example, I can't manage releases, create epic(?) issues, and a few other things. That's all well, but the problem's that getting a JIRA license gives you the ability to manage your issues at a more granular level, until you realise that you also need Stash to create epic(?) issues. I got into JIRA for a few months, and was disappointed by it. I've been considering moving some of my private repos to GitHub.
- tragic 12y ago
  We use jira at work, and there are definitely epics available...?
  - nevi-me 12y ago
    Interesting, I was on 6.0-6.1, and unless I'm completely wrong, I went a month seeing an 'activate Stash to use this feature' button/link. If you've had epics before then, then I was probably doing something wrong.
  - oblio 12y ago
    His point is that because of Jira, Bitbucket can't have epics. Cannibalizing sales.
- rlaanemets 12y ago
  Bitbucket has issue with cross-referencing. You can reference an issue from an issue but to make a two-way reference you need to edit both. This is a showstopper for projects that use tracker for planning too, not just for logging bugs.
  - sytse 12y ago
    GitLab B.V. CEO here, consider using GitLab, it adds a cross-reference when you reference another issue (can be in the same or another repo, even across organizations).
    - noobhater 12y ago
      i can't stand when a tech company can't innovate their own webpage more than using a standard Bootstrap template any noob developer can use. No offense to your product I'm sure it's great. I just don't understand why every company, especially in the tech field can't even design their website to be just a little bit unique.
      - mixmastamyk 12y ago
        And why should it be unique? Do you require that with every entity you deal with?
        noobhater 12y ago
        Yes :)
- davidgerard 12y ago
  Ha. Yeah, we use paid Github and paid Jira at work, and it's an idyllic combination. In a couple of decades, Jira is the closest I've ever seen to the Bugtracker That Doesn't Suck Much.
- Cogito 12y ago
  I'm not sure what exactly you are referring to, but let me give a quick break down of the options here (my day job is primarily consulting around the Atlassian stack of tools). JIRA itself is highly configurable out of the box and most aspects of the tool can be configured however you like. If you want a record ("issue type") called "Epic" it is easy to configure JIRA to have it. It is also easy - for some definition of easy! - to customise the data you collect for these records ("fields"), when that data is displayed ("screens"), and the lifecycle through which it will progress ("workflow"). However! Most people want to use Epics as part of an Agile methodology, and Atlassian provides a batteries-included solution called "JIRA Agile". If you saw an 'activate to enable Epics' button it was almost certainly for JIRA Agile (previously GreenHopper) though I don't recall seeing this button myself. JIRA Agile is nice for many reasons, even for people who don't follow an Agile methodology, IMO primarily because it provides a simpler user experience for many people - most installations I've seen have it. Stash itself is a fairly well targeted piece of software. It manages git repositories, and provides tools to help with that and integrate with external systems. Provisioning projects->repositories->branches and the permissions around them, pull requests, forks, hooks, automations, and integrations. It's also fairly easy to extend with add-ons from the marketplace or that you have written yourself. The integration between Stash and JIRA is good, but is not much more than showing branches, pull requests, and commits that a JIRA issue has been referenced in. Hope that helps
nstart 12y ago
I stick with bitbucket mainly because of the pricing schemes. I create a lot of tiny private repos for company related work, sometimes just scripting type programs with only 5 files in it, and I can't afford to pay for each of those on github. Otherwise, github is just the best in the business in every aspect
- sytse 12y ago
  GitLab B.V. CEO here, what do you think about the interface of GitLab? You can use it for free on GitLab.com and we try to make the interface as clean as possible. (also, we're hiring for an interaction engineer)

Also like Bitbucket, and agree with the interface. They made things responsive a while ago, and there were lots of complaints about the 'create a README' decision as a space-waster, they haven't done anything about it since. I like their revenue model, but because of the existence of JIRA and Stash, Atlassian are refusing/reluctant to improve the issue tracker in Bitbucket. For example, I can't manage releases, create epic(?) issues, and a few other things. That's all well, but the problem's that getting a JIRA license gives you the ability to manage your issues at a more granular level, until you realise that you also need Stash to create epic(?) issues. I got into JIRA for a few months, and was disappointed by it. I've been considering moving some of my private repos to GitHub.

tragic 12y ago
We use jira at work, and there are definitely epics available...?
- nevi-me 12y ago
  Interesting, I was on 6.0-6.1, and unless I'm completely wrong, I went a month seeing an 'activate Stash to use this feature' button/link. If you've had epics before then, then I was probably doing something wrong.
- oblio 12y ago
  His point is that because of Jira, Bitbucket can't have epics. Cannibalizing sales.
rlaanemets 12y ago
Bitbucket has issue with cross-referencing. You can reference an issue from an issue but to make a two-way reference you need to edit both. This is a showstopper for projects that use tracker for planning too, not just for logging bugs.
- sytse 12y ago
  GitLab B.V. CEO here, consider using GitLab, it adds a cross-reference when you reference another issue (can be in the same or another repo, even across organizations).
  - noobhater 12y ago
    i can't stand when a tech company can't innovate their own webpage more than using a standard Bootstrap template any noob developer can use. No offense to your product I'm sure it's great. I just don't understand why every company, especially in the tech field can't even design their website to be just a little bit unique.
    - mixmastamyk 12y ago
      And why should it be unique? Do you require that with every entity you deal with?
      - noobhater 12y ago
        Yes :)
davidgerard 12y ago
Ha. Yeah, we use paid Github and paid Jira at work, and it's an idyllic combination. In a couple of decades, Jira is the closest I've ever seen to the Bugtracker That Doesn't Suck Much.
Cogito 12y ago
I'm not sure what exactly you are referring to, but let me give a quick break down of the options here (my day job is primarily consulting around the Atlassian stack of tools). JIRA itself is highly configurable out of the box and most aspects of the tool can be configured however you like. If you want a record ("issue type") called "Epic" it is easy to configure JIRA to have it. It is also easy - for some definition of easy! - to customise the data you collect for these records ("fields"), when that data is displayed ("screens"), and the lifecycle through which it will progress ("workflow"). However! Most people want to use Epics as part of an Agile methodology, and Atlassian provides a batteries-included solution called "JIRA Agile". If you saw an 'activate to enable Epics' button it was almost certainly for JIRA Agile (previously GreenHopper) though I don't recall seeing this button myself. JIRA Agile is nice for many reasons, even for people who don't follow an Agile methodology, IMO primarily because it provides a simpler user experience for many people - most installations I've seen have it. Stash itself is a fairly well targeted piece of software. It manages git repositories, and provides tools to help with that and integrate with external systems. Provisioning projects->repositories->branches and the permissions around them, pull requests, forks, hooks, automations, and integrations. It's also fairly easy to extend with add-ons from the marketplace or that you have written yourself. The integration between Stash and JIRA is good, but is not much more than showing branches, pull requests, and commits that a JIRA issue has been referenced in. Hope that helps

nstart 12y ago

I stick with bitbucket mainly because of the pricing schemes. I create a lot of tiny private repos for company related work, sometimes just scripting type programs with only 5 files in it, and I can't afford to pay for each of those on github. Otherwise, github is just the best in the business in every aspect

sytse 12y ago
GitLab B.V. CEO here, what do you think about the interface of GitLab? You can use it for free on GitLab.com and we try to make the interface as clean as possible. (also, we're hiring for an interaction engineer)