Evan Fishman - Quely for Jira Atlassian Partner

I completely agree. The missed opportunity is massive. Sharing what is going well and actively swarming on blockers turns it into something the team actually wants to attend. The planning stage is the biggest factor here, and I have a ton of thoughts around it. The little things matter, the scattered info that leads to…

Exactly!

100%! Technical PM, Technical PO, whatever comes next, is just the org trying to solve an ownership problem with a label. It never works.

Exactly. The title doesn't matter as long as the context survives the handoff. Whether it is a PM or a PO. The moment one person talks to the customer and another writes the ticket, context starts to leak.

Sure @Michael Karl here you go. 

It is! @Debbie Lindsey 

@Michael Karl You just described the job nobody formally owns: context custodian. Multiple Jiras.Updates split between comments, docs, chat threads, and meetings.Then a recurring “reset meeting” Quely is basically built for people doing exactly what you’re doing now, trying to stop context from leaking across Jira…

@Calogero Bonasia This is exactly how we envisioned Quely. A living context bound to the work itself. Just to note though, we are a completly different tool from the OG Rally, had to switch our name to Quely to avoid the confusion. We should chat sometime so I can show you where we are at with this vision. 

Yayyyy🚀

Thank you!

Thanks, @Mia Tamm _Simpleasyty_ exactly! Async isn’t about doing things later, it’s about keeping the work (and all its context) moving without the meeting bottleneck. Glad the visual helped make that clear 🙌 Let's have a chat about Quely. 

@Elena_Elevatic How about a space where all your important context related to a particular task or work item lives? Engineering context could be pulled from Jira, Slack, meetings, confluence etc, Same for all agile ceremonies. 

Love this@ @Andy Gladstone The only snag though is exactly what you said: "we need to take the time". That’s the part most teams struggle with, remembering to document, having someone own it, doing it consistently, and keeping it up to date.

@Namita AwasthiWe should talk! We built Quely to do exactly this but on a much larger, more structured scale. You nailed it: the problem isn't just task overload. It's context fragmentation. And no amount of task reprioritization or “meeting hygiene” fixes that if teams are still stitching context together from 7 different…

Alright Thanks. 

@Kate C_ Tried getting the Partenr lozenge but I do not have the "Get access to the Partner Portal." option on the support link. 

Totally agree with you @__ Jimi Wikman 

Thanks @SilkeS Will do just that. 

Exactly. That is why we built Rally for Jira. It is a project I am passionate about. 

Haha Thanks Shivam. Will you be at Team'25?

@Tinker Fadoua Lol, no😅

🤣🤣🤣

Haha, I love the proactiveness 😅😅

I try to take a quick cup of coffee lol. 

@Stephen_Lugton, Love this! We should have a chat about how Rally mirrors your layout almost exactly lol. 

@Vishal Biyani Agendas will always lead to more productive meetings, at Rally I try to set up agendas at least a week before, this way everyone has sometime to review. One nice thing I do weekly is set up Rally sessions for the whole team where everyone can contribute to the agenda via our plugin. So basically, it is a…

@Stephen_Lugton This is quite similar to what we do at Rally. We all have our calendars synced, so any 2 team members who want to collaborate could do so if they find the opening. We sometimes have our standups this way too, but most times, we do everything else on our app. Eating our own dog food lol Especially for…

@Barbara Szczesniak 😅😅

@Christopher Holmes Thank you! This is actually a workflow I have not thought of lol. Currently working on a doc feature for Rally for Jira too. 

@Dmitry Astapkovich _Colined_ Will reach out. Thanks.