3 ms·

Above a certain level of complexity, Jira is the best work tracking and managing solution I've worked with. Its curse, is its developed by Atlassian. A compan

by ep103 5y ago

Above a certain level of complexity, Jira is the best work tracking and managing solution I've worked with. Its curse, is its developed by Atlassian. A company that was capable of buying Stash, and, somehow, somewhat, turned that codebase into what we now know as bitbucket.

dljsjr 5y ago
Other way around. They made Stash in house, they bought BitBucket, and rebranded Stash as BitBucket Server. The BB acquisition happened before Stash was released but Stash was not an acquisition.
- ep103 5y ago
  I was of the impression that they bought Stash, renamed it to Bitbucket Server, and stopped development, while slowly attempting to reimplement stash code into Bitbucket cloud, one feature at a time?
  - dljsjr 5y ago
    Nope, you can see a condensed version of their acquisition history on their Wiki page for more proof: https://en.wikipedia.org/wiki/Atlassian#Acquisitions_and_product_announcements https://en.wikipedia.org/wiki/Atlassian#Acquisitions_and_pro... When BitBucket was acquired they were cloud only, and when Stash launched it was on-prem only. We used Stash and BitBucket Cloud around that time at the place I was working and I can definitely tell you that on-prem Stash was definitely not a reskinned on-prem BitBucket Cloud; for one I’m pretty sure BitBucket Cloud was written in Python (Django) and Stash was a typical Atlassian Java product.
hpoe 5y ago
If your org needs that much complexity it probably is at a point that the time and money wasted waiting for Jira todo things is probably small in comparison to the rest of the wasted efficiency.
- ep103 5y ago
  The main issue with Jira is it allows you to build far, far too complicated workflows. And Jira + someone who believes in job security via complexity and obfuscation can be a horrific combination. The best part of Jira is because it is so flexible, no matter how your process slightly deviates from a basic trello-like board, you should be able to make one or two adjustments in JIRA and have it reflect that. That's not true of literally any other workflow piece of software I've used, and I've used a ton. That said, because all the other types of workflow management software I've used are significantly more opinionated and limited, they also limit how bad of a process a bad project administrator can create in them as well.

by ep103 5y ago

dljsjr 5y ago

Other way around. They made Stash in house, they bought BitBucket, and rebranded Stash as BitBucket Server. The BB acquisition happened before Stash was released but Stash was not an acquisition.

ep103 5y ago
I was of the impression that they bought Stash, renamed it to Bitbucket Server, and stopped development, while slowly attempting to reimplement stash code into Bitbucket cloud, one feature at a time?
- dljsjr 5y ago
  Nope, you can see a condensed version of their acquisition history on their Wiki page for more proof: https://en.wikipedia.org/wiki/Atlassian#Acquisitions_and_product_announcements https://en.wikipedia.org/wiki/Atlassian#Acquisitions_and_pro... When BitBucket was acquired they were cloud only, and when Stash launched it was on-prem only. We used Stash and BitBucket Cloud around that time at the place I was working and I can definitely tell you that on-prem Stash was definitely not a reskinned on-prem BitBucket Cloud; for one I’m pretty sure BitBucket Cloud was written in Python (Django) and Stash was a typical Atlassian Java product.

hpoe 5y ago

If your org needs that much complexity it probably is at a point that the time and money wasted waiting for Jira todo things is probably small in comparison to the rest of the wasted efficiency.

ep103 5y ago
The main issue with Jira is it allows you to build far, far too complicated workflows. And Jira + someone who believes in job security via complexity and obfuscation can be a horrific combination. The best part of Jira is because it is so flexible, no matter how your process slightly deviates from a basic trello-like board, you should be able to make one or two adjustments in JIRA and have it reflect that. That's not true of literally any other workflow piece of software I've used, and I've used a ton. That said, because all the other types of workflow management software I've used are significantly more opinionated and limited, they also limit how bad of a process a bad project administrator can create in them as well.