jira

My Q&A for InfoQ on Keeping Distributed Teams in Sync

~ maratkiniabulatov ~ 3 Comments

I spoke with Ben Linders of InfoQ (thrilled to be published at that website!) about challenges and communication patterns for Distributed Teams, uncovering bits of my Atlassian Summit 2018 speech. The biggest challenge of distributed teams is communication, which is essential for establishing ground rules on collaboration. Shifting working hours to accommodate each other and team liaisons … Continue reading My Q&A for InfoQ on Keeping Distributed Teams in Sync

Telegram -> Stride Migration Experience

~ maratkiniabulatov ~ 1 Comment

Recently I hosted Minsk Atlassian User Group, where I shared our experience on migrating to Stride and gave the analogy between Stride, and Russian word 'Stradai' (-> eng.: 'Suffer'). I'll explain the analogy later. Hence the 'Napalm Death' song 'Suffer' joke on the first slide 🙂

Given that a lot of people use Telegram as a corporate messenger, and given all of the telegram-blocking happening in Russia currently, it's pretty relevant to write about alternatives. We at SkuVault migrated due to the need of user control, but migration experience is relevant to many other teams.

Jira: removing transition from current status to itself (if All -> transition is turned on)

~ maratkiniabulatov ~ Leave a comment

Small and duct-tapey resolution for the time, when you have an All -> [statusName] JIRA workflow transition. By default, it results in the following: Default Ticket Screen shows transition from current to current status, among others. So e.g., you have an In Progress ticket, you have the transition to the very same In Progress. To … Continue reading Jira: removing transition from current status to itself (if All -> transition is turned on)