Hugo Mora Insider

Perfect, that's cleaner than I assumed — equal runway for everyone. Thanks for clarifying. The other one still stands though: any plan to let people know when a Champion picks up an idea they suggested in the comments?

Hi Monique, Thanks for laying out the statuses — the part I appreciate most is that Closed (Won't Do) comes with a stated rationale. Most ideation boards quietly let things rot, and "no, because X" is far more respectful of people's time than permanent silence. Two bits of friction worth thinking about: The non-Champion…

Hi @Man What strikes me about this thread is that every answer so far solves visibility. Structure for the Gantt, Confluence and JSM for intake, Projects and Rovo for stakeholder updates. All of it answers "what is happening." Almost none of it answers "is this project healthy," which is the question a PMO actually gets…

@s_gridnevskii the time-boxed VIP admin is a good pattern, and I'd ask one question about it: what actually revokes it when the clock runs out? Jira Cloud won't do it for you — there's no expiry on group membership or on the admin role. So "for a specific period" is only as real as whatever removes the person, and in most…

Hi @Vladymyr Postnov I think there is a fundamental issue with using negative reviews as a proxy for the overall quality or reliability of an app. People are much more likely to leave a review when something goes wrong than when everything works as expected. A satisfied user normally just continues using the product. A…

Thanks @Sami Shaik — and your framing of it is better than mine was. "A diff you check, not a claim you trust" is the whole idea in one line, and it generalises past this migration: any vendor-run change you can't rehearse, the report tells you what the tool believes it did. Four things I'd add, because they're what makes…

Hi @William Gunkel Nice to meet you and welcome to this groups Cheers, --Hugo

Hi @Sami Shaik Since your constraint is that you can't rehearse, I'd focus everything on the one thing you can do without EAP access: capture the before state while it still exists. The reason your question 2 is hard is that you're depending on the tool to tell you what it removed. You don't have to. Before migration day,…

Hi everyone. Answering your questions in order, from a consultant's sample rather than a single instance. What keeps coming back: select-list options (weekly, in every instance), group membership (weekly), adding an existing field to a screen (monthly), a new status or a tweaked transition (monthly), permission changes for…

Hi @Danny Daniel Welcome to the Atlassian group!! 

I work on a Solution Partner, so take the perspective with that in mind — but I'd push back on the framing of the title, if not on the frustration behind it. "Ignoring feedback" and "considered the feedback and decided differently" look identical from outside, and they're not the same thing. This thread is actually…

@Ren Takahashi your four-step pattern is solid — the thing I'd add is a way to stop needing it so often. Rather than branching the answer, ask for one artefact that resolves the ambiguity for free: the URL of the page they're looking at. Company-managed Jira Software project URLs carry a /c/ segment…

@Ben Dangelmayr _Dangel Studio_ — the handover case is the one worth solving separately, because it's the only one process can't fix. Validators protect the future; the existing backlog just needs counting once. A few things that make that count survivable: Don't audit everything. Pick only the fields that feed a report…

Great article @Trudy P Claspill — the framing of "you're matching a real need to a sustainable solution, not gatekeeping" is the part I'd want every admin to internalise. One thing I'd add from the migration side: the cost of the conversation you didn't have shows up years later, and it lands on someone else. A big part of…

Hi Alexander, Short answer: don't fight it with executions — just declare the plugins with a configuration block and AMPS merges it in. AMPS doesn't bind surefire/failsafe to the lifecycle the normal way. It invokes those goals itself (via MojoExecutor) so the ITs run in the window between the host app starting and…

Two different things, and only the first is required to ship. 1. Make the app usable (developer console). A 3LO app is private by default — only you can use it. Go to your app → Distribution → enable sharing, filling the mandatory fields: Vendor (your company), Privacy policy URL, and the personal-data declaration (if Yes,…

Hi Alejandro, Your state wasn't tampered with — it lost exactly one level of percent-encoding on the way back. Compare the two values character by character: * outbound: ...FWMm4Aa%252F20w7... and ...E694Y%253D * callback: ...FWMm4Aa%2F20w7... and ...E694Y%3D After the single decode any query parser performs, your endpoint…

Hi Dimitrios, We’ve released PMO Assessment & Reports for Jira—a lightweight way to see Cost, Quality, and Time for your projects in one place. Create Accounts to group projects, plug in hour costs/budgets, refresh metrics on demand, and spot quality issues (including a helpful “MUDA” waste report). Works on Jira Cloud.…

Hi Andy, We’ve released PMO Assessment & Reports for Jira—a lightweight way to see Cost, Quality, and Time for your projects in one place. Create Accounts to group projects, plug in hour costs/budgets, refresh metrics on demand, and spot quality issues (including a helpful “MUDA” waste report). Works on Jira Cloud. Try it…

Hi @Lana Montgomery I sent an application for being Atlassian Champion and I didn't receive any feedback... Could you please check it its status? Thanks a lot. Hugo

Hi Nic, Heap is setup with 4 GB. I think that we have located the function on the JQL. I will update this issue.Thanks,--Hugo

Hi! More info about this issue We have reproduce the error on a side environment, using a JQL like this: {code} project = PROYECT1 AND "CustomFieldA" in (VALUE1,VALUE2, VALUE3) AND issueFunction in issueFieldMatch("", labels, "1.61.0") ORDER BY updated DESC {code}We have desactivated module "Scripted JQL Function"…

Hi Jamie, "TEST-1" was a really bad name for a test custom field. :-( It wasn't an issue. I've updated the code. Thanks, --Hugo