video1.0<iframe src="https://www.loom.com/embed/544c021b5ea5473d92374ad791428d8b" frameborder="0" width="1920" height="1440" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>14401920Loomhttps://www.loom.com14401920https://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.eyJicyI6Imxvb20tbWVkaWEtY29udGVudCIsImF1ZCI6InRkcC1vcy1hcmNoZXR5cGUiLCJuYmYiOjE3ODc5MTE5MTcsInRpIjoiOTA4ZWY1N2YtYzAxMy00YTE5LWE1YzItMjk3ZWY2NTc5ZTg2IiwiYWRpIjoibG9vbS9sb29tIiwiaXNzIjoibWljcm9zLWdyb3VwL3RkcC1vcy1hcmNoZXR5cGUiLCJwaWQiOiI0YzdiOGJjOC0zNGJmLTRiM2ItODEyMy0wN2NlNzIwM2Y5ZTQiLCJ3YSI6ImZhbHNlIiwib2lkIjoic2Vzc2lvbnMtdGh1bWJuYWlscy01NDRjMDIxYjVlYTU0NzNkOTIzNzRhZDc5MTQyOGQ4Yi0wOWRmZjczMzkwZWUxODQzLmdpZiIsImV4cCI6MTc4NzkxMjIxNywiaWF0IjoxNzg3OTExOTE3LCJqdGkiOiIwZmM4MDE1Mi05NDZjLTQxM2MtYmIwMC0yNThhN2I2Zjk2MzkifQ.staidgSdb-gACLsy7kclI_t2XmqRit1niilrLDvBu3qm1awdmRiXDTy5se0YPl5HLWWdpvcj-IAlSL06p_jcqOHKhqkw8HuZHnI3b3n9Dq6pCiFBOcP8lbRxphig7xYMJjmkdbPwWYeudqwaog1ZnfihcOnXqQOb5rdlaOniUUeu18cdCLG39Eg84lRKUFnFX9wR4lc5byGlR1sgE96KsX_1bieEpNc3RQMgo70ls7uVm9kgmZBUhmWzT10XMuNLHazZ0FQt0ON10h5kXPrgAvO_El8ud1I9RFW5LhK-FUo09Bn9s0EOjhvzjeRdQCvJ7ILceTwyhrc5j6uFbKbEgQ&Expires=1787998318&Signature=NUUqZqOJnMou74tI0TSLX7sPlseo9R0hzTN2FTDQ9k90PSeXxuiGdLB5T5VftQC%7E1sniSrPzQUDaV8qK9OP57%7Echq13s-EK6yhrNLhUMc7eENAjwXSD%7EAWXwXjqoYVr1eV8ymb19doiD21smtg5sWgaZans6V9XaXmSwDDX4tZxSH-cOll%7Ex3ebsFHtEZ4Hjl8FM0TjvaPFAfCbk9Mjs5qNxqwRIwrJFpYliPqtnw5hcFlYf5B%7ELL-C86TnXu36ScW27mwvAl14DYdZ9lLH7-RDlZ3KsyVTZnbnwk6vLuTHWn44MPKA8XDtOiDa5EDt9L3ozm-HjJp16r8OivWBIYw__&Key-Pair-Id=KQOSYIR44AIC03632.308The 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. ### Problem and objectives: guided autonomy trade-off 3:52 - Described the core trade-off: consistency and governance versus team speed and autonomy when running Jira at scale. - 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. - Stated objective: introduce "guided autonomy" so admins set boundaries and teams operate without waiting on central admins. - 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. - Promised demos, early access/beta availability, and details on how to get access later in the session. ### Admin agent demo: request handling and automated field operations 7:13 - 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. - 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. - Reuse decision: agent detected an existing isRTB field and proposed reusing it rather than creating a duplicate. - 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. - 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. - 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. ### Agent q&a and roadmap clarifications 22:12 - Admin Agent early access: signup link will be shared; current first version focused on fields and impact analysis before one-click execution. - Handling broad impact: roadmap includes branching options (copying schemes/screens) to isolate changes when many spaces are affected. - 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. - Semantic similarity: agent will perform semantic search to surface similar fields/statuses to avoid near-duplicate entities; calibration will be needed to balance relevance. - Consumption: agent usage consumes the same Rovo credits/usage model as existing Rovo agents. - Next phases: help users raise requests through agents, support cleanup and deduplication, and expand to other configuration domains after fields are stable. ### Space policies and templates demo: controlled team-managed spaces 27:26 - Role-play: engineering lead requested nine team spaces; admin considered team-managed spaces but worried about configuration sprawl. - 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). - 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. - Global statuses: introduced ability to use global statuses within team-managed spaces to standardize status names across team spaces. - 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. - 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. ### Space policies q&a, licensing, and policy expansion 41:40 - 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). - Licensing: Space Policies are available across all license levels for team-managed spaces. - Rationale: space policies provide balance between team autonomy and organizational consistency (common language and reporting) rather than removing team-managed freedom entirely. - 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. - Conflict resolution: currently requires manual resolution for existing spaces; automated conflict resolution is a longer-term objective. ### Wrap-up, availability, and next steps 47:49 - 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. - 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. - 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. - 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. - Timeboxed Q&A: five minutes left for final questions before closing. ### Final technical questions and customization notes 52:32 - 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. - Admin Agent customization: upcoming milestone will allow uploading organizational knowledge bases so the Admin Agent respects org-specific standards, naming, and procedures. - 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. - Follow-up offer: product team (Dmitry) offered to share contact email in chat to discuss deeper feature requests and use cases outside the session.