Hey team! Atlassian just announced some big news - Jira and Confluence Data Center will reach end of life on March 28, 2029. The Quick Timeline: - Dec 2025 - No new DC apps in Marketplace - March 2026 - No DC sales for new customers - March 2028 - Existing customers can't expand DC - March 2029 - Game over for DC Why the change? Simple: 99% of Atlassian customers are already on Cloud or migrating there (including 75% of enterprise customers). The market has spoken - Cloud wins for speed, cost, and AI features. What this means for you: If you're on DC, you've got 3.5 years to migrate. Sounds like plenty of time, but trust me - complex migrations take longer than you think, especially with: - Custom configurations - Integrations - Large datasets - Training needs My advice? Don't wait until 2028. Start planning now while you have options and aren't competing with everyone else scrambling at the last minute. Currently helping several organizations with their DC → Cloud migrations. If you're facing this transition and want to chat strategy, drop me a DM. Happy to share what I'm seeing work (and what to avoid). Anyone else dealing with this announcement? What's your timeline looking like? P.S. - Bitbucket DC gets special treatment with a hybrid license option, so source code folks have more flexibility.

Hi all, I'm new to Jira. We're thinking of starting to use Jira to assist with department data and technical requests, so I was wondering if you can set up approval processes in Jira? Can this be added to a workflow? Many thanks! 🙂

Hey, it's Mike and in today's episode, I'll dive deep into the world of issue collectors and showcase how they can transform how you gather and manage feedback for your WordPress website. An issue collector is an invaluable tool that allows you to seamlessly collect feedback, bug reports, and feature requests from your website visitors. By implementing an issue collector, you'll empower your users to share their thoughts and experiences, helping you identify areas for improvement and prioritize your efforts. We'll cover the following topics: - Selecting the right issue collector tool for your needs - Creating and customizing your issue collector form - Embedding the issue collector code into your WordPress site - Managing and responding to incoming feedback effectively Don't forget to like, share, and subscribe :) https://www.youtube.com/watch?v=Y08Frl4MB7k

Hi everyone! I am perfectly aware that JIRA doesn't allow to assign an issue to multiple owners. However, some activities are carried out together by the whole team. For example, an inspection or a meeting. Therefore, usually I do it this way: I clone the issue multiple times as many as the people are and then I assign each of them to the various owners. But it is not as quick as it is said. Is there a smarter way to do that?

Hey team, Me again here. Hope everyone's doing well. As I dive deeper into Jira, there's one thing that's got me scratching my head a bit – Jira components. I've gone through the basics, but I must confess, I'm still not 100% on the ball with how they function in real-world scenarios. For those of you seasoned in using components, could you share some insights or practical examples of how you utilize them effectively in your projects? I'm especially keen on understanding their advantages over labels or custom fields, and how they might best serve someone in a business analysis role like mine. Thanks in advance for your wisdom and patience. It's a learning curve, and I appreciate all the support! Cheers,