Shivam Sharma - Optimizory Community Champion

A new refreshed evening with the community forums; let's dig it out 😀

Hey @Dori Burnett, 1. Yes, you can spot me in RAI, Amsterdam, mingling with my team and fellow champions. 2. I’m particularly excited to learn more about JSM agents, the product collection, and the concept of no-coding agents.

@Yana Misiura_BrizoIT It was really amazing working on this with you; you made the whole thing easy, and especially the credits for designing goes to you only 😃 Looking forward to whatever we cook up next 🙌

Thank you @Yana Misiura_BrizoIT! The pleasure was all mine. Really enjoyed putting this one together with you and the BrizoIT team, and Yes, I'm really excited for what's next 😃

Hi @Singh_ Rahul_ENG_ , Welcome to the Atlassian Community! Opening each story one by one just to check its linked issues is the real time sink here. There's an app that puts the whole thing on one screen: Report X It maps to your ask like this: * Plug in your JQL: Your project = ABC AND issuetype = Story AND sprint =…

Hi @Yana Misiura_BrizoIT Love this initiative; I’ll send you an email soon so we can collaborate on it

Hi @Amruta , Welcome to the Atlassian Community You've actually hit one of Jira's real limitations here. The backlog and board are filter-driven, not relationship-driven, so even with the Parent field set correctly, Jira has no native concept of "show me everything linked to Project-A's epics." Any JQL approach ends up…

Hi @Belinda Pereira , Welcome to the Atlassian Community! Importing HTML files one by one will technically work, but you'll lose the tree structure and the links between requirements, which sounds like the main thing you're trying to preserve. A better path is to export from ADO as CSV instead of HTML; I believe ADO…

Hi @sravani vennapusa , Totally doable in Jira; the question is just how clean you want the sequence to be. Native automation can get you the TR0000001 format using a smart value like TR{{issue.key.substringAfter("-").leftPad(7,"0")}}, but the number stays tied to the Jira work item key. So you'll see gaps when work items…

Thank you, @Anahit Sukiasyan !! 😃

Hi @Kamil Stepien , The Release Package container approach makes sense, most teams land here once native fixVersions start feeling limiting. Custom work item type with dates, links, and version association works well in practice. One tip: decide early whether these live in a dedicated "Releases" project or inside each…

Sure @Piyush Annadate _ACE Pune_ I'd love to join you on a large scale!! 🙌🏻

Amazing write, @Piyush Annadate _ACE Pune_ I totally get how challenging it can be to manage a chapter with everything happening parallelly. The approach you guys have is truly awesome! I’m doing something similar on a smaller scale

Hi @Sanjay! Yes, what you're describing is very much achievable. Custom ID for Jira lets you define custom ID patterns for Jira issues, so instead of being limited to default Jira keys, you can create meaningful, structured identifiers like B1, C1, or hierarchical formats like A1-1, B1-1 for child/subtasks. You have full…

This article is a perfect example. That community can be a valentine for you as well. 😝

That's actually a really good write!! Kudos to you @Liam Do - DevSamurai for sharing this, for marketplace partners, I believe it's a game changing thing, because right now, vendors play with keywords to list them on top, but now who's the real problem solver getting privileged.

Welcome to the club @Ritik Singh 🎉

Congratulation everyone! We did a great demo battle even before the Appy hour party. Now waiting for the final battle!!

Before casting your vote, don’t miss ‘Baseline X’ — it’s the quiet powerhouse in this list. Give it a quick look, you might be surprised 👀

Sherlock just tried using Jira and immediately asked for Links Explorer ‘Links Explorer’ is already solving the cases your work items didn’t even know they were part of Take a peek before your vote goes missing in action 🕵️‍♂️🍻

Thanks for sharing the API details and the GitHub link, @Rustem Shiriiazdanov _Actonic_! I’ll check them out and explore the data a bit. And I’m definitely looking forward to your follow-up article — the trends you’re tracking sound really interesting Really appreciate you putting this together!

That's a good write @Rustem Shiriiazdanov _Actonic_ I've kept this article open in one of my tabs for couple of weeks to do a read, but didn't get enough to read it all, but today I did, I read the whole article, and have to say that, really great findings, that's actually helpful, comparisons from previous year, gives a…

Thanks, @Stephen_Lugton Totally agree, RM is the only thing that keeps everyone aligned and stops the chaos 😅 Glad the post hit the mark!

Great point @__ Jimi Wikman — estimation is definitely a key metric in the requirement process. It ties directly into risk and resource management, ensuring teams can balance cost, time, and priorities across both CapEx and OpEx initiatives. Without it, even well-documented requirements can fall short in execution. Thank…

Hi @Morgan Watts , Thank you for sharing your approach of how you are achieving the CLM system within the ecosystem only, that seems like a good one, we do have similar kind of approach in our Jira add-on "Pact" Just few things weren't there in our app, but happy to discuss more with you in detail, if you're open for that

Hi @Kate C_ , I have access to the partner portal and also have all the links in my profile to our marketplace listing of our apps on atlassian marketplace, but on the "Request Partner lozenge on Atlassian Community" page, I won't be able to see any option to apply or request for the Partner lozenge. Would you be able to…

A good recap of the guidelines & community terms; even if someone isn't aware of them, that person will get a fair idea of all the stuff

That's really a smart quiz for this smart community that we are building together, not alone. It reminds me of the call that I had when I was onboarding as a community champion. Good to have a hands-on understanding of the guidelines and the rules of the community and the recap of everything we do every day to get a fair…

Kudos to you, guys! Keep going.

Heard a lot about this at a community event. The turnaround of this great use case, which impressed me a lot, will be taking up or announcing a session on this in the future.