Geekly Articles each Day
📜 ⬆️ ⬇️

The experience of the transition to the Atlassian Stride (from the word Suffer)


Due to the blocking of the telegram, it would be important to write about the Atlassian Stride, how we switched to it, and what pleasures the solutions from the beloved Atlassian encountered.


Atlassian Stride was launched in November 2017 as a replacement for cloud-based HipChat. De facto, the main competitor is, of course, Slack. I will try to compare Stride with Slack, and Telegram from the text correspondence.


pros


Embedding in the Atlassian Ecosystem, user control


The biggest plus is, of course, seamless integration into the Atlassian ecosystem. You have jira, confluence - and a single user account, where you can control access to different pieces and features of these two applications. And now you have the third application - Stride, and chat user management is available from the same admin panel.


Accordingly, not only the resolution, but also full control, with the transparency of the chat, and removing the user from all applications simultaneously (jira, confluence, bitbucket, ..., stride) comes from one admin area. Even the right to configure the old admins do not have much.


In the telegraph we had personal accounts, and this did not work well with control over them by the organization (certainly, it would be possible to distribute virtual numbers and make corporate accounts, but this is too inconvenient to maintain). So if you are locked into the Atlassian ecosystem and infrastructure -> it’s convenient to have Stride as a platform for calls and messaging.


In terms of price, Stride $ 3 / user, which is cheaper than Slack.


Video calls


For some, this is not such a big plus, but after the Telegram (IM) + Skype bundle (calls) it has become much more convenient to have everything in one application.


Integration with Atlassian products via bots



It is not something out of the box, but nevertheless it is configured in two clicks. After inserting the ticket number, we will see a preview-card of the task, with information about the priority, to whom the description is assigned, components.





Suffering


With the seemingly Stride, this is a normal platform, it is still raw, and those basic features that we consider should be present by default in any product with messaging, are implemented in it crookedly.


Video calls



To begin with, I’ll make a remark that Slack is bad in video calls, and we haven’t found anything better than Skype in quality. But Stride breaks through the Slack-ovskoy bottom! In particular,



Okay, enough about video calls, there are a lot of other disadvantages!


Basic functionality




Alerts


Argued that the products Stride'a set the task of the team to make the most invisible sound alert. Mission accomplished!
The sound is so invisible that if you listen to music, it is difficult to notice. If you left, then the background noise in the office will easily block the sound of the notification (someone will say, they say, then you will come and see the notification on the screen - read on =). Accordingly, a person may simply not notice and not respond to an important message (for example, the server crashes or tests in Jenkins).


There is no mute function for chats, which means that there is a lot of unnecessary noise and pop-ups.


No indication "message read." And it is not clear, poke a colleague so that he looked, or he is already aware of the problem.


The phone does not receive a third-quarter alert. But when they come - then there is a chance not to get them on the desktop application! It happens, you see a long message in the phone, you climb to read from the laptop - but it is not there. Treated with a restart strayd.


Jira bot


Let's be honest, integration with Jira in the same Slack is currently more convenient than in Stride. Jira Bot will throw out thumbnails of tickets of such size that the closest analogy in my head is a worm that was used to dig cities in Gears of War 2 — ticket cards take so much space.



JSON and API


As our DevOps have noticed, Stride should be fed exclusively with parted JSON, he himself refuses to do this (as Telegram)


In the rest


Stride is a normal, working solution. It does not make communication impossible, and if you are not critical of the disadvantages described above, and you care for and cherish the Atlassian ecosystem (even after new updates to the Jira interface), then it is really convenient. We, in general, have become more accustomed, and are watching the dynamics of bug fixes and adding features. But if you do not need it, and you already use Slack, then it is easier to sit on it.


The guys in Stride are in a hurry with the updates, trying to fix the shortcomings in order of priority, known only to the product manager of the Australians (who leaves critical comments on Jira hang in feature request for 7 years). Telegram and Slack have been developing for years, to become a good and convenient solution. I think, and Stride comes to this, time will tell. However, the practice of blocking shows that Stride (Amazon Cloud) and Slack are unavailable in Ufa, and Telegram, as usual, is still working.


Sent Requests to Stride Task Tracker



')

Source: https://habr.com/ru/post/354536/

More articles:


All Articles