{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/544c021b5ea5473d92374ad791428d8b\" frameborder=\"0\" width=\"1920\" height=\"1440\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1440,"width":1920,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1440,"thumbnail_width":1920,"thumbnail_url":"https://cdn.loom.com/os/loom-media-content/loom/a436116f-02ce-4520-8fbb-7301462a1674/1621dc1f-3702-4525-84ba-fad829566798/sessions-thumbnails-544c021b5ea5473d92374ad791428d8b-09dff73390ee1843.gif/binary?authToken=eyJraWQiOiJtaWNyb3MtZ3JvdXAvdGRwLW9zLWFyY2hldHlwZS9wM2I1NW1kbGEzamc3MWM1IiwiYWxnIjoiUlMyNTYifQ.eyJicyI6Imxvb20tbWVkaWEtY29udGVudCIsImF1ZCI6InRkcC1vcy1hcmNoZXR5cGUiLCJuYmYiOjE3ODc5MTE5MzksInRpIjoiMTQwZjc5ODktYTBjOC00ZGNlLWI3MGUtMmM3ZDc5NjcxYjI1IiwiYWRpIjoibG9vbS9sb29tIiwiaXNzIjoibWljcm9zLWdyb3VwL3RkcC1vcy1hcmNoZXR5cGUiLCJwaWQiOiI0YzdiOGJjOC0zNGJmLTRiM2ItODEyMy0wN2NlNzIwM2Y5ZTQiLCJ3YSI6ImZhbHNlIiwib2lkIjoic2Vzc2lvbnMtdGh1bWJuYWlscy01NDRjMDIxYjVlYTU0NzNkOTIzNzRhZDc5MTQyOGQ4Yi0wOWRmZjczMzkwZWUxODQzLmdpZiIsImV4cCI6MTc4NzkxMjIzOSwiaWF0IjoxNzg3OTExOTM5LCJqdGkiOiI3YTJjMjk3Ny1hNmE2LTRhNDEtYTRjYi0xODRiMDM4ZWQ3NTEifQ.jikawuIRPUqlLx0Roczd425wJ7U9R277kAn_8vaY5y20JUupCF0oKERoI6wlLrpqaMR7ksyMV8feB1gzVcb2J_Szlr36NOtCgB8NW9-f984ntz1ZILdVYibUWrNuodaOKPmWo1VnlofkDzLudW2JPfE0rU8eEUZITKrwVCjeoF9ucKWst0pK31MG7tmoCRmhgAaC3k104fqqBAHU8fqvY7nThNRL1zenJsXylhz4g8s719J1MTrSjEOO1iYbDcC-Io8SI2asb10kwpDbP_RAm6xdEOhTWZXmkV6Dxb45i8d5VMKgT0TV5PQNaJuyt08Sge1Lv10xiN1MQfY4DpmZzA&Expires=1787998340&Signature=H9ImO7cg493hCHAnk0lZaJfXwK83uMb55egzNYxABbfprs9vgkTAi2sFR1E9AqB8toOb2rnRfr9WPEZ6Ld%7EbLRSwHSKikVBiR2EmZ2PvrjxDbRzk3YSp8DJWgLau1KpQp4s%7EXm6WY4lNuKWuhSuezmDx2IP67Ih-IhWnA0pmOHSF0NuIM-2GM9-FbnmdzGAqjlO5fzRcVx%7E5IR1SB5-wTbGhY8b7tercgPXkIulA-fy7jL3OJmJR6rL0571%7E2KMP85IgF7ybTmMWi4C-EcY4JTzdfBExZh8YpkW6DeGKLdOEPUwBZb11QhBo9zrCZ75TwaqwAvQqfC0EWmqp6LTutQ__&Key-Pair-Id=KQOSYIR44AIC0","duration":3632.308,"title":"ACE Admin session","description":"The meeting presented two features to scale Jira administration: an Admin Agent (LLM-powered) to analyze, plan, and apply field-related configuration changes with impact analysis and verification; and Space Policies plus custom templates to safely delegate team-managed space creation while enforcing global fields/statuses. Demos showed role-played requests, the agent reusing an existing field and applying changes, and an admin creating a policy-backed template that a team lead used to create spaces without creating new local fields. Next steps: Space Policies will be available in beta in coming days, the Admin Agent is in early access with a signup link, and roadmap items include workflow support, JSM support later, semantic similarity detection, cleanup tools, and uploadable knowledge bases for organization-specific standards.\n\n### Problem and objectives: guided autonomy trade-off 3:52\n\n- Described the core trade-off: consistency and governance versus team speed and autonomy when running Jira at scale.\n- Identified pain: thousands of small admin approvals gradually erode standards and reporting accuracy; some admins spend up to 30 hours/week on operational support and configuration requests.\n- Stated objective: introduce \"guided autonomy\" so admins set boundaries and teams operate without waiting on central admins.\n- Announced focus areas: team-managed and company-managed spaces, space policies and templates, global fields/statuses for team-managed spaces, and an Admin Agent for company-managed changes.\n- Promised demos, early access/beta availability, and details on how to get access later in the session.\n\n### Admin agent demo: request handling and automated field operations 7:13\n\n- Role-play: engineering lead (Ira) raised a ticket requesting a new checkbox field (isRTB) to be added to work types in a company-managed space.\n- Admin Agent: admin opens the agent, instructs \"implement the request from this ticket,\" and the agent analyzes site configuration to find existing fields, screens, schemes, and potential downstream impacts.\n- Reuse decision: agent detected an existing isRTB field and proposed reusing it rather than creating a duplicate.\n- Planning: agent generated a detailed plan listing steps (associate field with field scheme, add to edit/view screens) and showed affected spaces and work types, enabling impact review before execution.\n- Execution and verification: admin applied the plan; agent executed steps, verified by sampling issues via JQL, retried if needed, and reported completion; user (Ira) confirmed field now appears.\n- Capabilities and limitations: first prototype focused on fields (create, associate, screens, contexts), early access only, and plans to expand to user-request flow, cleanup/duplication detection, and broader configuration domains.\n\n### Agent q&a and roadmap clarifications 22:12\n\n- Admin Agent early access: signup link will be shared; current first version focused on fields and impact analysis before one-click execution.\n- Handling broad impact: roadmap includes branching options (copying schemes/screens) to isolate changes when many spaces are affected.\n- JSM and forms: JSM support is planned but lower priority; agent starts with Jira-specific operations and may handle JSM when the configuration model aligns.\n- Semantic similarity: agent will perform semantic search to surface similar fields/statuses to avoid near-duplicate entities; calibration will be needed to balance relevance.\n- Consumption: agent usage consumes the same Rovo credits/usage model as existing Rovo agents.\n- Next phases: help users raise requests through agents, support cleanup and deduplication, and expand to other configuration domains after fields are stable.\n\n### Space policies and templates demo: controlled team-managed spaces 27:26\n\n- Role-play: engineering lead requested nine team spaces; admin considered team-managed spaces but worried about configuration sprawl.\n- Space Policies concept: new beta feature to apply policies to team-managed spaces limiting what teams can add (current policies: only global fields, only global statuses, or both).\n- Admin workflow: admin applied a policy (only global fields and statuses) to a team-managed space, reviewed conflicts (local statuses/fields), resolved conflicts by removing non-compliant statuses, and achieved compliance.\n- Global statuses: introduced ability to use global statuses within team-managed spaces to standardize status names across team spaces.\n- Templates: admin saved the compliant space as a custom template (template for leadership syncs), scoped template creation permission to a specific group (engineering leadership), and changed image/description for clarity.\n- Outcome: admin provided the template to the requester (Ira); requester created the first space from the template, could not create new local fields due to policy, but could add existing global fields (e.g., is cross-functional) without opening a ticket.\n\n### Space policies q&a, licensing, and policy expansion 41:40\n\n- Availability: Space Policies will be in beta and rolling out to everyone in coming days via the Jira site Beta features page (system settings -> Beta features).\n- Licensing: Space Policies are available across all license levels for team-managed spaces.\n- Rationale: space policies provide balance between team autonomy and organizational consistency (common language and reporting) rather than removing team-managed freedom entirely.\n- Future policy candidates: exploring additional rules such as workflows, controlled lists of templates/spaces per team, and curated lists of allowed fields to further scale team-managed spaces safely.\n- Conflict resolution: currently requires manual resolution for existing spaces; automated conflict resolution is a longer-term objective.\n\n### Wrap-up, availability, and next steps 47:49\n\n- Summary message: guided autonomy combines standards with team autonomy; teams operate from global lists so reporting and consistency hold while admins reduce time on routine changes.\n- Availability timeline: Space Policies beta expected in days; Admin Agent is in staged early access with a signup form link shared in chat and planned beta later.\n- Admin Agent roadmap: planned beta opt-in for admins to enable agent without contacting product team; longer-term features include automated conflict resolution and broader domain support.\n- Action items: attendees can enable beta features via the Beta features page in system settings, sign up for Admin Agent early access, and expect more communication through chat and follow-ups.\n- Timeboxed Q&A: five minutes left for final questions before closing.\n\n### Final technical questions and customization notes 52:32\n\n- Resolution schemes: attendee suggested resolution schemes similar to priority schemes; product team currently has no roadmap item but is open to follow-up to explore use cases and workarounds.\n- Admin Agent customization: upcoming milestone will allow uploading organizational knowledge bases so the Admin Agent respects org-specific standards, naming, and procedures.\n- Workflow support: workflows are the immediate next domain after fields on the Admin Agent roadmap; team will stabilize field mechanics first, then extend the same mechanics to workflows and other configuration areas.\n- Follow-up offer: product team (Dmitry) offered to share contact email in chat to discuss deeper feature requests and use cases outside the session."}