<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" version="2.0">
<channel>
<title>
Comments for Work Life by Atlassian </title>
<atom:link href="https://www.atlassian.com/comments/feed" rel="self" type="application/rss+xml"/>
<link>https://www.atlassian.com/blog</link>
<description>Unleashing the potential of all teams with tips, tools, and practices</description>
<lastBuildDate>Wed, 14 Jan 2026 21:50:28 +0000</lastBuildDate>
<sy:updatePeriod>
hourly </sy:updatePeriod>
<sy:updateFrequency>
1 </sy:updateFrequency>
<item>
<title>
Comment on How to excel at asynchronous communication with your distributed team by The Coffee Kitchen Myth: Why Proximity Is Overrated and Digital Colleagueship Actually Works - MI Hub </title>
<link>https://www.atlassian.com/blog/communication/asynchronous-communication-for-distributed-teams#comment-25412</link>
<dc:creator>The Coffee Kitchen Myth: Why Proximity Is Overrated and Digital Colleagueship Actually Works - MI Hub</dc:creator>
<pubDate>Wed, 14 Jan 2026 21:50:28 +0000</pubDate>
<guid isPermaLink="false">https://www.atlassian.com/blog/?p=54373#comment-25412</guid>
<description>[&#8230;] Hallway proximity is synchronous by default: you catch someone, interrupt them, and hope the moment is good. Async collaboration flips the burden: it allows people to respond with context, time, and thought—often producing better decisions and less resentment. Atlassian&#8217;s guidance on asynchronous communication emphasizes intentional habits and shared norms so distributed teams can align without constant real-time interruption, outlined in Atlassian&#8217;s async communication playbook. [&#8230;]</description>
<content:encoded><p>[&#8230;] Hallway proximity is synchronous by default: you catch someone, interrupt them, and hope the moment is good. Async collaboration flips the burden: it allows people to respond with context, time, and thought—often producing better decisions and less resentment. Atlassian&#8217;s guidance on asynchronous communication emphasizes intentional habits and shared norms so distributed teams can align without constant real-time interruption, outlined in Atlassian&#8217;s async communication playbook. [&#8230;]</p>
</content:encoded>
</item>
<item>
<title>
Comment on Caelor talks Forge and Shoppie, their latest innovative app by anm"ala dig till binance </title>
<link>https://www.atlassian.com/blog/developer/caelor-talks-forge-and-shoppie#comment-25411</link>
<dc:creator>anm"ala dig till binance</dc:creator>
<pubDate>Wed, 14 Jan 2026 18:10:31 +0000</pubDate>
<guid isPermaLink="false">https://www.atlassian.com/blog/it-teams/caelor-talks-forge-and-shoppie#comment-25411</guid>
<description>Thanks for sharing. I read many of your blog posts, cool, your blog is very good.</description>
<content:encoded><p>Thanks for sharing. I read many of your blog posts, cool, your blog is very good.</p>
</content:encoded>
</item>
<item>
<title>
Comment on Building an enterprise-grade Jira bulk operations Forge app by Designing a Forge app - Work Life by Atlassian </title>
<link>https://www.atlassian.com/blog/developer/building-an-enterprise-grade-jira-bulk-operations-forge-app-2#comment-25410</link>
<dc:creator>Designing a Forge app - Work Life by Atlassian</dc:creator>
<pubDate>Wed, 14 Jan 2026 17:41:12 +0000</pubDate>
<guid isPermaLink="false">https://www.atlassian.com/blog/?p=70370#comment-25410</guid>
<description>[&#8230;] abstractions and architecture choices. I&#8217;ve used this approach for previous apps such as the bulk work item operations app I wrote about previously. You can also apply the same approach to your Forge apps;- begin with a deep understanding of the [&#8230;]</description>
<content:encoded><p>[&#8230;] abstractions and architecture choices. I&#8217;ve used this approach for previous apps such as the bulk work item operations app I wrote about previously. You can also apply the same approach to your Forge apps;- begin with a deep understanding of the [&#8230;]</p>
</content:encoded>
</item>
<item>
<title>
Comment on More power and more control: the power-ups menu is moving by бнанс </title>
<link>https://www.atlassian.com/blog/add-ons/power-ups-menu#comment-25409</link>
<dc:creator>бнанс</dc:creator>
<pubDate>Wed, 14 Jan 2026 16:06:43 +0000</pubDate>
<guid isPermaLink="false">https://www.atlassian.com/blog/it-teams/power-ups-menu#comment-25409</guid>
<description>Thank you for your sharing. I am worried that I lack creative ideas. It is your article that makes me full of hope. Thank you. But, I have a question, can you help me? https://accounts.binance.com/ru-UA/register-person?ref=JVDCDCK4</description>
<content:encoded><p>Thank you for your sharing. I am worried that I lack creative ideas. It is your article that makes me full of hope. Thank you. But, I have a question, can you help me? <a href="https://accounts.binance.com/ru-UA/register-person?ref=JVDCDCK4" rel="nofollow ugc">https://accounts.binance.com/ru-UA/register-person?ref=JVDCDCK4</a></p>
</content:encoded>
</item>
<item>
<title>
Comment on More power and more control: the power-ups menu is moving by Registro </title>
<link>https://www.atlassian.com/blog/add-ons/power-ups-menu#comment-25408</link>
<dc:creator>Registro</dc:creator>
<pubDate>Wed, 14 Jan 2026 15:48:01 +0000</pubDate>
<guid isPermaLink="false">https://www.atlassian.com/blog/it-teams/power-ups-menu#comment-25408</guid>
<description>Thanks for sharing. I read many of your blog posts, cool, your blog is very good.</description>
<content:encoded><p>Thanks for sharing. I read many of your blog posts, cool, your blog is very good.</p>
</content:encoded>
</item>
</channel>
</rss>