what is wrong with the sourcetree dev culture?

[Patrick Permien]

Hey folks,

I'm following these tickets for ages now, and they really make the Atlassian product development and/ or developer culture look bad.

This ticket was created in 2018, "gathering interest" for years and then closed with a faulty implementation.

https://jira.atlassian.com/browse/SRCTREE-6224

I then created a follow-up bug which is again in "gathering interest". I have rarely seen a case where a software company so blatantly ignores fellow developers from their own community. I believe this is embarrassing for Atlassian as a company. Just scroll through the comments, you will see the disappointment.

Atlassian doesn't listen, doesn't react properly, seemingly doesn't care. Why? And what can be done to get the development culture for Sourcetree back on track?

[Mochnant]

I've noticed the lack of progress on very basic features that I've followed as tickets for years.  One of the reasons I migrated away from BitBucket to a competitor.

I still use SourceTree, though, so I get to continue to enjoy the slow dev cycle (shameless plug for SRCTREE-7077).

[Mochnant]

One option to fix this very old problem of little/no dev support is outlined in this community post from 2017:  Open source the SourceTree source code