1. 39
  1.  

  2. 19

    Atlassian uses GitHub for all its projects. I think it keeps Bitbucket for existing customers that still pay but probably ships no features as it’s a waste of time. I am always surprised how so many companies still use Atlassian when for every single product they have, a better alternative exists.

    1. 8

      Jira is the most configurable issue tracker i know.

      Confluence is the best wysiwyg wiki i know.

      For Bitbucket I’m not sure, but it might also win for configurability.

      1. 28

        Jira is the most configurable issue tracker i know.

        That’s why it’s so bad. It makes busywork a full time job.

        1. 5

          An old go-to joke of mine is that I’d like to work at Atlassian for a year just to see the world’s only correctly-configured Jira install.

          1. 2

            I dunno. A lot of other tooling assumes a lot about workflows that you might not think about because it suits your workflow. I work in the games industry at a small shop. The server team, web team, gameplay teams, QA teams, art teams, content writing teams, and translation teams all have very different workflows, so the configurability is helpful. We have a yearly release cycle so we tweak the Jira workflows about once a year. But we also use BitBucket and it does indeed suck a whole lot, as does Confluence.

          2. 11

            How configurable do you need your issue management to be? Linear does pretty much everything one may need for issue tracking and does it fast.

            For Confluence, I had personal bad experience where I dreaded adding content to it because of its wysiwyg editor amongst horrible search and again super slow UI.

            Things may have changed though.

            1. 5

              Linear is probably great for software projects. I think Jira is used much more broadly to track any given process in enterprises.

              1. 2

                Yes, JIRA is also used basically as a project management toolkit that goes beyond issue tracking. Epics, boards, service tickets are all things I’ve seen used at a huge international corporation.

                That doesn’t mean it’s good, just what it’s used for. I think GitLab does a lot of this stuff.

              2. 2

                It isn’t just about issue management being configurable, it’s also about reporting and statistics-collecting being configurable. If your boss wants this report done this way, helping them deal with disappointment isn’t always the optimal answer, and Enterprise Software is Middle-Management-Ware first and foremost.

                1. 1

                  Linear doesn’t even have on-premise installs, does it?

                  1. 1

                    Atlassian is phasing out on-premise installs of Jira.

                    https://www.atlassian.com/blog/announcements/journey-to-cloud

                    On February 2, 2021 Pacific Time (PT), the following changes will go into effect:

                    • End of new server license sales: You can no longer purchase or request a quote for a new server product.
                    • Updates to server prices: We will implement new prices for server renewals and upgrades.

                    On February 2, 2024 PT, the following change will go into effect:

                    • End support for all server products: This means that support and bug fixes will no longer be available for your server products.
                    1. 1

                      Have a guess why people using Jira are looking at alternatives that have a comparable feature set, one of the features being on-premise installs.

                      1. 1

                        My point exactly.

                2. 6

                  Does anyone have any recommendations for issue management that aren’t online-only? We’re using Jira now, but since Atlassian has decided to stop developing the on-premises variant we’re in need of something new (eventually, we’ve got a couple of years to transition).

                  Both Asana and Linear (which got recommended in this thread) seem to be online only.

                  1. 2

                    there’s always bugzilla…

                    1. 3

                      Upstream Bugzilla is very far from the nice experience you get on bugzilla.mozilla.org though. You have to work a lot to get it to be not really ugly.

                    2. 1

                      Fossil might be worth a look? It’s from the SQLite folks I think.

                      https://www.fossil-scm.org/

                      (It does a lot more than issue tracking though.)

                      1. 1

                        My team is also looking into alternatives to JIRA and also wants to keep it on-prem. I would be curious as well as to what solutions others come up with.

                        1. 2

                          Paid GitLab? We use it even as an internal forum.

                          1. 1

                            We actually are already using paid gitlab on prem. Not sure if thats being considered.

                        2. 1

                          Why do you guys need on-prem? Regulatory issues?

                          1. 7

                            We’d like to keep our secrets where we can see them, I suppose.

                            Edit: and also not be auto-updated to newer versions of a tool that could mess up our internal workflow with no chance of going back to a version that worked the way we liked it. Or have the provide go out of business. Or other similar issues.

                            1. 1

                              Redmine?

                            2. 4

                              Yes. Storing critical data on other peoples’ computers is simply not an option.

                              1. 4

                                Amen. It’s nice to use other peoples’ computers sometimes, for “unimportant” things. (Scare quotes used there, because I include things that are only unimportant owing to careful contingency planning that makes it so in that bucket.)

                                But for critical, core things, the question should be “what have you done to make it OK for this to live in the cloud?” Not “why do you need on-prem?”

                                1. 3

                                  I used to work in a place where adopting new tools was pretty straightforward if you needed them, but they required a reasonable bit of planning ahead, after the company got burned many years before when a software package they used got retired and a whole product line got delayed because there was no way to test them on time. There was a small sub-section in the proposal that read “Migration Path” and basically required you to list how you’d move to another solution should the current one stop working for whatever reason (company goes under, licensing costs become prohibitive etc.) Due to that sub-section the company was basically fully on-prem.

                                  When the expected lifetime of a company is in the 3-5 years range (ship something, get acquired) you can use pretty much anything from anywhere, but these guys had been in business for a very long time. They’d outlived virtually all of their suppliers, sometimes by decades.

                                  1. 1

                                    Same story here. Dropping/rejecting a lot of dependencies based on “we are unsure whether this stuff will exist in 20 years/built by Google”.

                          2. 1

                            Jira is the most configurable issue tracker i know.

                            I recommend to check out Asana. It comes pretty close.

                            1. 1

                              Asana doesn’t even have on-premise installs, does it?

                                1. 0

                                  Did you click on the link?

                                  (Assuming you did, guess why people using Jira are looking at alternatives with a comparable feature set, one of the features being on-premise installs?)

                                  1. 1

                                    Because Jira’s UX sucks. Which is what the submission is about. Except it’s about Bitbucket.

                                    I get the point you’re making but self-hostedness didn’t come up so far in this thread. Only UX and flexibility.

                                    So if this is a requirement for you that’s fine and I acknowledge you can’t use Asana. Just stop implying I did not read the submission or am missing the point of the discussion.

                                    1. 2
                                      1. 3

                                        self-hostedness didn’t come up so far in this thread

                                        Let me rephrase: I was responding to a poster that did not bring up self-hosted as requirement or apprechiated feature. I would not respond to a statement about Jira being the most configurable issue tracker if I didn’t consider Asana to be comparable in that regard.

                          3. 2

                            The hosted version of bitbucket (as opposed to bb server which is a completely separate thing for self hosting) is surely on life support at this point.

                            Then again, I think it’s hard to say it’s ever not been on life support, with issues like this one being open 10 years without even commitment to implement, much less actual implementation.

                            1. 4

                              For a while BitBucket offered some pretty decent competition to GitHub; for example the whole “copying code” thing from this article was pretty borked on GitHub too up until 2 or 3 years ago. Even though BitBucket was always a “GitHub clone” some features were done better in BitBucket IMHO. It had stuff like proper code reviews way before GitHub had.

                              But at some point it was pretty clear GitHub was on the winning side and they seemed to have just given up. Some features even regressed and became worse. It’s a shame in way, because it had a lot of potential and could have been what GitLab is today. The Atlassian acquirement was both a blessing and a curse, but ultimately more curse than blessing.