What's the sense of naming virtually different Atlassian Products identical?

[Johannes Kilian]

Does the identical naming of (functional) different products by Atlassian make sense (beside marketing)?

• Bitbucket Server and Bitbucket Cloud
• SourceTree for Windows and for Mac

Those products pairs do have the same target (hosting repositories, GUI for git) - but completly different functionality. This is very annoying when searching for support/help: you find an answer for your  SourceTree-question  - and the feature is not available for your Sourcetree, as it's on the other OS. (Same for example for Bitbucket plugins ...)

Maybe Atlassian plans to unify those products, but I doubt they ever will (see: https://answers.atlassian.com/questions/188551)

I cannot see any sense behind this - execpt marketing ...

[raj]

I can speak for rebranding Stash to Bitbucket Server. We discovered that customers were frequently confused between Stash and Bitbucket. We would occasionally hear - how can we get Stash in the cloud or how can we get Bitbucket behind the firewall? So we wanted to simplify the naming and make it similar to other products in the Atlassian family like Confluence or HipChat. See here if you have more questions: https://confluence.atlassian.com/display/BitbucketServer/Bitbucket+rebrand+FAQ

[Johannes Kilian]

Doing so, you just helped users/newbies/boneheads, who are not able to differntiate between two different products with similiar functionality - but you hamper the daily life of most of your higher skilled users.

This seems to be a general tendency: Fishing for newbies by offering some shiny new names or features, ignoring the needs of high leveled, long time users (or even worse: intimidate high leveld users). Best example are the recent "enhancements " of Sourcetree 1.8 which were mainly visual enhancements(???) to get a shiny blinky mainstream flat design to satisfy the needs of some GUI-freaks, but introducing myriads of bugs and NO new features - which were often demanded by the mass of your main users (you just have to look at the feature requests for SourceTree).

Those products are no mainstream products, but products for high skilled developers (and thoese people should be able to understand that STASH and Bitbucket are different products - if not, I doubt their skills...) - so why running after the mainstream?

[Phill Fox]

I share your pain. And with the split of JIRA in to JIRA Core, JIRA Software and JIRA Service Desk the pain is multiplied... Where do you look if you have both JIRA Software and JIRA Service Desk... [Running for the padded room to bang head on wall...]