Victoria Golovtseva

Victoria GolovtsevaAug 20, 2026

I just realized that this week I’ll work from 𝗳𝗼𝘂𝗿 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝘁 𝗹𝗼𝗰𝗮𝘁𝗶𝗼𝗻𝘀. And I kind of love that. :) Different desks. Different views. Different cities. Today’s office happens to be a terrace overlooking Warsaw — which is making it particularly hard to complain about the commute. For me, this is still one of the best things remote work has given us. Not simply “working from home.” 𝗧𝗵𝗲 𝗳𝗿𝗲𝗲𝗱𝗼𝗺 𝘁𝗼 𝗱𝗲𝗰𝗶𝗱𝗲 𝘄𝗵𝗲𝗿𝗲 𝘄𝗼𝗿𝗸 𝗳𝗶𝘁𝘀 𝗶𝗻𝘁𝗼 𝘆𝗼𝘂𝗿 𝗹𝗶𝗳𝗲. Sometimes that means my usual desk and a very predictable cup of coffee. Sometimes it means working from another country, moving between places during the week, and opening my laptop somewhere with a completely different view. The work is still the work. But changing the environment gives me energy, curiosity, and that small feeling of adventure that I definitely don’t want to lose. After years of remote work, I can say this part still hasn’t become ordinary for me. Four locations in one working week. And Warsaw from the terrace today. ☕️ I’ll take it. :) What’s your favorite place you’ve ever worked from? 👋 𝘕𝘦𝘸 𝘩𝘦𝘳𝘦? 𝘐'𝘮 𝘝𝘪𝘤𝘵𝘰𝘳𝘪𝘢, 𝘱𝘢𝘳𝘵 𝘰𝘧 𝘵𝘩𝘦 𝘵𝘢𝘨 𝘈𝘵𝘭𝘢𝘴𝘴𝘪𝘢𝘯 𝘊𝘰𝘮𝘮𝘶𝘯𝘪𝘵𝘺 𝘊𝘩𝘢𝘮𝘱𝘪𝘰𝘯𝘴 :) 𝘊𝘰𝘯𝘵𝘦𝘯𝘵 𝘔𝘢𝘳𝘬𝘦𝘵𝘦𝘳 𝘢𝘯𝘥 𝘊𝘦𝘳𝘵𝘪𝘧𝘪𝘦𝘥 𝘊𝘢𝘳𝘦𝘦𝘳 𝘊𝘰𝘢𝘤𝘩. 𝘏𝘦𝘳𝘦 𝘐 𝘴𝘩𝘢𝘳𝘦 𝘈𝘐 𝘸𝘰𝘳𝘬𝘧𝘭𝘰𝘸𝘴 𝘧𝘰𝘳 𝘮𝘢𝘳𝘬𝘦𝘵𝘪𝘯𝘨 𝘢𝘯𝘥 𝘤𝘰𝘯𝘵𝘦𝘯𝘵 𝘵𝘦𝘢𝘮𝘴, 𝘸𝘳𝘪𝘵𝘦 𝘢𝘣𝘰𝘶𝘵 𝘈𝘵𝘭𝘢𝘴𝘴𝘪𝘢𝘯 𝘵𝘰𝘰𝘭𝘴 𝘢𝘯𝘥 𝘱𝘳𝘰𝘤𝘦𝘴𝘴𝘦𝘴, 𝘢𝘯𝘥 𝘰𝘤𝘤𝘢𝘴𝘪𝘰𝘯𝘢𝘭𝘭𝘺 𝘵𝘩𝘪𝘯𝘬 𝘰𝘶𝘵 𝘭𝘰𝘶𝘥 𝘢𝘣𝘰𝘶𝘵 𝘈𝘐, 𝘵𝘩𝘦 𝘫𝘰𝘣 𝘮𝘢𝘳𝘬𝘦𝘵, 𝘢𝘯𝘥 𝘸𝘩𝘦𝘳𝘦 𝘢𝘭𝘭 𝘰𝘧 𝘵𝘩𝘪𝘴 𝘪𝘴 𝘩𝘦𝘢𝘥𝘪𝘯𝘨. 🙂 𝘍𝘰𝘭𝘭𝘰𝘸 𝘮𝘦 𝘧𝘰𝘳 𝘮𝘰𝘳𝘦 🔔

Victoria GolovtsevaAug 13, 2026

Every time Atlassian ships something new, we at TitanApps run it against a real workflow of our own before writing about it. Teamwork Graph, Rovo Search, Rovo Studio, agents in Jira, all of it.  𝗕𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝗮 𝗥𝗼𝘃𝗼 𝗔𝗴𝗲𝗻𝘁 𝗳𝗼𝗿 𝗼𝘂𝗿 𝗼𝘄𝗻 𝗿𝗲𝗹𝗲𝗮𝘀𝗲 𝗰𝗮𝗱𝗲𝗻𝗰𝗲 𝘄𝗮𝘀 𝘁𝗵𝗲 𝗼𝗯𝘃𝗶𝗼𝘂𝘀 𝗻𝗲𝘅𝘁 𝗼𝗻𝗲. Oleksandra Sokol, our Product Lead, took our sprint and release process and rebuilt it in Rovo Studio. We ship one release per sprint, so the loop runs 26 times a year: create the next sprint and version, assign issues to the current release, summarise what changed on each ticket, draft release notes, transition everything to Released when the version ships. The most useful thing that came out of it was a question worth answering before you open Rovo Studio. Not "which of these tasks are AI tasks." That question goes in circles. The one that actually sorts the work: 𝗱𝗼𝗲𝘀 𝘁𝗵𝗶𝘀 𝘁𝗮𝘀𝗸 𝗵𝗮𝘃𝗲 𝗼𝗻𝗲 𝗰𝗼𝗿𝗿𝗲𝗰𝘁 𝗼𝘂𝘁𝗰𝗼𝗺𝗲, 𝗼𝗿 𝗱𝗼𝗲𝘀 𝗶𝘁 𝗻𝗲𝗲𝗱 𝗷𝘂𝗱𝗴𝗺𝗲𝗻𝘁? Creating a sprint has one correct outcome. Setting a Fix version has one correct outcome. Those belong in Automation for Jira. Summarising a comment thread needs judgment. Drafting release notes needs judgment. Those belong to an agent. It came out as four automation rules, two of which call a custom Sprint & Release Manager Agent. A few things worth knowing before your first build: • You do not have to start in the rule editor. Describe the outcomes to Rovo Chat and it will scaffold the rules with a Build automation button on each one. Real onramp if writing automation from scratch makes you nervous. • Raw prompts inside automation rules run thin. Moving the instructions into a dedicated agent produced sharper output and stopped the same prompt being duplicated across rules. • Comments from the agent are attributed to the agent. When your team is still deciding how far to trust AI-assisted work, being able to see who wrote a comment does quiet, useful work. The honest limit, in Oleksandra's words: if you already know Jira Automation well and have complex rules running, Rovo will slow you down. The carousel has the shape of the build.  The full walkthrough is on Atlassian Community, with all four rules, the agent instructions, and the five ways to trigger an agent. Link in the comments. 👇 #AtlassianCommunityChampions 👋 𝘕𝘦𝘸 𝘩𝘦𝘳𝘦? 𝘐'𝘮 𝘝𝘪𝘤𝘵𝘰𝘳𝘪𝘢, 𝘱𝘢𝘳𝘵 𝘰𝘧 𝘵𝘩𝘦 𝘵𝘢𝘨 𝘈𝘵𝘭𝘢𝘴𝘴𝘪𝘢𝘯 𝘊𝘰𝘮𝘮𝘶𝘯𝘪𝘵𝘺 𝘊𝘩𝘢𝘮𝘱𝘪𝘰𝘯𝘴 :) 𝘢𝘯𝘥 𝘢 𝘊𝘰𝘯𝘵𝘦𝘯𝘵 𝘔𝘢𝘳𝘬𝘦𝘵𝘦𝘳 𝘣𝘦𝘩𝘪𝘯𝘥 𝘵𝘩𝘦 𝘣𝘦𝘴𝘵𝘴𝘦𝘭𝘭𝘪𝘯𝘨 𝘈𝘵𝘭𝘢𝘴𝘴𝘪𝘢𝘯 𝘔𝘢𝘳𝘬𝘦𝘵𝘱𝘭𝘢𝘤𝘦 𝘈𝘱𝘱 𝘚𝘮𝘢𝘳𝘵 𝘊𝘩𝘦𝘤𝘬𝘭𝘪𝘴𝘵. 𝘏𝘦𝘳𝘦 𝘐 𝘴𝘩𝘢𝘳𝘦 𝘈𝘐 𝘸𝘰𝘳𝘬𝘧𝘭𝘰𝘸𝘴 𝘧𝘰𝘳 𝘮𝘢𝘳𝘬𝘦𝘵𝘪𝘯𝘨 𝘢𝘯𝘥 𝘤𝘰𝘯𝘵𝘦𝘯𝘵 𝘵𝘦𝘢𝘮𝘴, 𝘸𝘳𝘪𝘵𝘦 𝘢𝘣𝘰𝘶𝘵 𝘈𝘵𝘭𝘢𝘴𝘴𝘪𝘢𝘯 𝘵𝘰𝘰𝘭𝘴 𝘢𝘯𝘥 𝘱𝘳𝘰𝘤𝘦𝘴𝘴𝘦𝘴, 𝘢𝘯𝘥 𝘰𝘤𝘤𝘢𝘴𝘪𝘰𝘯𝘢𝘭𝘭𝘺 𝘵𝘩𝘪𝘯𝘬 𝘰𝘶𝘵 𝘭𝘰𝘶𝘥 𝘢𝘣𝘰𝘶𝘵 𝘈𝘐 🙂 𝘍𝘰𝘭𝘭𝘰𝘸 𝘮𝘦 𝘧𝘰𝘳 𝘮𝘰𝘳𝘦 🔔

Victoria GolovtsevaAug 3, 2026

If someone wrote a book about your career 15 years from now… What would the title be? Let’s not try to imagine your job title at a time or how your brand will grow. Let’s also forget your current job title and LinkedIn headline. Let’s try to craft The story. I think we spend too much time planning the next role and too little time thinking about the next chapter. When I look back, almost none of the biggest turning points in my career were part of “the plan.” They came from saying yes to something that didn’t fit my current title: * writing instead of analytics; * moving from education business into IT; * becoming part of the Atlassian ecosystem; * learning AI before it became an expectation; * starting career consulting alongside marketing. Each step looked disconnected at the time. Only later did they become a coherent story. AI makes this even more important. Technical skills have a shorter lifespan than they used to. Your ability to connect different domains, learn continuously, and reinvent yourself is becoming a competitive advantage. So here’s a Monday exercise. Instead of asking: “Where do I want to work next?” Try asking: “If someone wrote a book about my career in 2040, what would I hope people learn from it?” The answer won’t tell you your next job. But it might tell you which opportunities are worth saying yes to this year. What would the title of your career book be? You can see mine below :) Sitting at the dawn with new book in hands I feel like I can actually write it one day. Why not - life is long game :)