Riddle: What's the best time to plant a tree?

[Marshall Walker Lee]

"The best time to plant a tree was 20 years ago. The second best time is now." — Proverb

For some of us (*coughs and looks in mirror*) growth isn't a linear path, it's a serious of semi-conscious advances and retreats. We learn when we can, when we must, when our curiosity is piqued—but we rarely learn at the precise moment when learning can unlock our growth. 

So, what's something about Atlassian apps and solutions (or more generally about teamwork and collaboration) that you've learned recently that you wish you'd learned much earlier?

[Elizabeth Nixon]

Jira Miscellaneous Workflow Extension!! Oh my goodness, what a joy this has become for me. I stumbled on it a few years ago, before I hit my Jira Admin stage. This year I've been able to really dive into it. My company is super tight on budget, and we won't upgrade to Premium (which I'm bummed about for many reasons) and the automations I created without JMWE started to exceed our monthly allowance. Then I realized that we had JMWE connected (from before we started crimping down on expenses) and I started learning and transitioning workflow rules to JMWE. I love it!

I know there is SO much more for me to learn, and I'm excited for what's to come. 

[Robert Leachman]

Digging deeper into ScriptRunner Behaviours, and now planting a tree in that hole :)

[Daniel Seiderer]

If the efforts by a group of people are co-ordinated well it becomes a true and truly rewarding team effort.

[Tracy B]

That using a Jira Two Dimensional Filter on a Confluence page is an excellent way to answer the question "which tasks are in which statuses, and who is doing them?"

[Cintia Csermák]

I used to see Jira and Confluence as separate tools, but linking them changed everything. Now we track alert-related tickets on a Confluence page via Jira labels, and it’s made collaboration so much smoother. I also love how easy it is to search and filter in Confluence. It really supports working together, not just documenting stuff.

[Derrick kibet]

The use of AI in ticket management is transforming every aspect of the process. From managing and responding to users, to asking AI to analyze a ticket, reading through Confluence troubleshooting guides, and providing resolution steps for reported incidents — it has never been this easy. Compared to 20 years ago, it’s a game changer! 😊

[Andy Gladstone]

Harvesting some low hanging fruit here (tree theme!) and stating that learning more about automations in Confluence has helped me and my team save time and enhance our documentation. The more docs we have in Confluence, and the easier it is to create and update them, the less tress we will need for hand written docs and notes!

[Debbie Brookfield]

I've learned that documenting as you go reaps many long-term benefits. For a long time our system documentation was buried in different Jira tickets, but now we use confluence to do the documenting and jsut use the JIRA ticket to refer to that documentation.  Keeps all the documentation in one place.

[Stephanie Poon]

Something I've been implementing recently is modelling active listening in workshops.

Not listening to respond, but listening to understand instead.

When collaborating, pausing and making space for silence to ensure everyone has a chance to contribute.

[MishManners]

When you are ready, when you have the tree, and when the weather and soil is right for the plant.

[Mirco Passeri]

50 Years ago!