Written by Ben Friedman, Atlassian expert & builder of JAMEs, the AI Jira administrator · Published · Updated
JAMEs is a supervised AI administrator that manages Jira configuration for you. Built with security and approval gates, it analyzes your Jira site directly to assess the impact of changes and carry them out, upon your confirmation.
Monitor progress, track changes and deploy with confidence.
JAMEs is currently in beta. For any questions, hello@viter.io.
What problem is JAMEs meant to solve? • How does JAMEs work? • Is JAMEs available today? • Why is JAMEs not on the Atlassian Marketplace? • Who should not wait for JAMEs?
JAMEs stands for Jira Admin Made Easy. It is an AI administrator for Jira built by Viter that analyzes your site to plan changes it can execute safely only after your approval. You describe a change in plain language, JAMEs plans it, you approve, and JAMEs does the rest while letting you track and monitor.
What does JAMEs do in Jira? • Which objects does JAMEs create and update? • What can JAMEs tell you about your automation rules, and what can it not? • Does JAMEs allow me to understand and track what it does? • When would JAMEs not match what you need?
JAMEs can query and update ten kinds of Jira object: users, permissions, custom fields, screens, workflows, projects, issue types and JSM request types. Automation rules are read only, boards are coming soon, and JAMEs cannot delete anything.
What happens when you ask JAMEs to change something? • What do you approve before anything runs? • How does JAMEs execute approved changes? • Wouldn’t a fully autonomous agent be more useful? • What separates JAMEs from a manual change or an admin script? • What if you need to undo a change? • What can’t JAMEs touch?
JAMEs never writes to Jira without an approved plan: it reads your existing configuration, proposes changes, a human approves, and execution runs through the Jira API under your own permissions. It has no delete capability at all.
What enforces the approval gate? • How is JAMEs’ access to your Jira bounded? • Why can JAMEs never delete anything? • What data does JAMEs keep, and where? • Which AI models process your data? • What record does JAMEs leave behind? • How do you recover when a change goes wrong? • What happens when you offboard from JAMEs?
JAMEs enforces security structurally: it writes nothing to Jira without an approved plan, its access is bounded by your own API token, it has no delete tools, and it stores minimal data in the EU with no training on customer content.
About the author
Ben Friedman is an Atlassian consultant and Forge developer with over 8 years of
hands-on Jira work, certified ACP-610, ACP-620 and ACP-120. He has delivered for hundreds of customers
across all business verticals, supporting their configuration, administration, and ongoing
support and maintenance. Ben is building JAMEs, the AI Jira admin.