Atlassian Government Cloud

Issue Templates Agent is available on Atlassian Government Cloud, so regulated teams can standardize Jira work without stepping outside a FedRAMP-authorized environment.

What is Atlassian Government Cloud?

Atlassian Government Cloud (AGC) is a dedicated cloud environment for U.S. government agencies and the partners who work with them. It runs on separate AWS infrastructure based in the US East/West regions and is authorized at the FedRAMP Moderate level, so it’s built to handle controlled, sensitive government workloads.

AGC is based on Cloud Enterprise foundations, so it carries over many of the same capabilities, such as multiple sites and Atlassian Analytics, while adding the compliance guarantees and dedicated support that regulated organizations need. Purchase and use of AGC is restricted to U.S. government agencies and organizations doing government-related work; it’s a separate offering from Atlassian’s standard Free, Standard, Premium, and Enterprise cloud plans, and each product (Jira, Jira Service Management, Confluence) is licensed under its own subscription.

AGC is one of the ways Atlassian now lets organizations with strict security needs adopt cloud, alongside Cloud Enterprise and the upcoming Atlassian Isolated Cloud for enterprises needing a dedicated, single-tenant environment.

Want the full background? Here’s where to read more:

• [PLACEHOLDER: our upcoming article comparing Atlassian Government Cloud and Atlassian Isolated Cloud] — link once it’s published.
• Atlassian Cloud Deployment Options — a comparison of Cloud Enterprise, Government Cloud, and Isolated Cloud.
• Atlassian’s overview of Government Cloud licensing and pricing — the official pricing and packaging details.

Is Issue Templates Agent available on AGC?

Yes. Issue Templates Agent is an approved app on Atlassian Government Cloud, so you get the same core template building experience you already know from commercial cloud, running inside an environment that meets FedRAMP Moderate requirements.

That means your agency or organization can:

• Build a centralized library of Jira issue templates for tasks, stories, epics, and more, without leaving the AGC boundary.
• Standardize intake for regulated processes, so every request captures the exact fields and data required, every time.
• Use templates in Jira Service Management portals too, so agents and customers get standardized request forms in AGC just like on commercial cloud.
• Apply templates through the Create Issue dialog, the Issue view, and Transition screens, plus through Jira Automation and our REST API, exactly as on commercial cloud.
• Rely on the same permission controls and audit log to keep your template library secure and accountable.

Since Issue Templates Agent runs inside AGC itself, there’s no external infrastructure involved and no data leaves the authorized environment as part of using the app.

How to install Issue Templates Agent on AGC

Installing on Atlassian Government Cloud works differently than on commercial cloud. Apps aren’t self-installed straight from the Marketplace listing — on AGC, only Atlassian support teams and certified partners can install apps for customers. Pricing may include installation and deployment costs and can vary by customer, so this is coordinated case by case rather than through a standard checkout flow.

If your organization is on AGC and wants Issue Templates Agent installed, the first step is to check with your site admin, who can help kick off the installation process with Atlassian. You can also contact Atlassian directly to get the process started.

Migrating templates from commercial cloud to AGC

If your organization is moving from Atlassian’s commercial cloud to Atlassian Government Cloud, you can bring your existing templates along using Issue Templates Agent’s built-in export/import feature. This isn’t automatic through Atlassian’s standard site migration tools, since it depends on our app’s own export/import mechanism, but the process is straightforward:

1. Export your templates. From your current commercial cloud instance, export your templates. This generates a .json file containing your template library.
2. Check whether the IDs match your new AGC instance. Projects, issue types, and custom fields may have different IDs once they’re set up in AGC. Before importing, check the .json file against your new environment:
   • If the projectID and issueTypeId values differ, update them to match the corresponding project and issue type in AGC.
   • Do the same for any customfieldID values, since our app relies on these matching exactly to map fields correctly.
   • Leave templateID values unchanged. Editing these isn’t necessary and can cause issues with the import.
3. Import the file. Once the IDs line up with your AGC instance, import the .json file, and your templates will be recreated there.

Because this relies on our app’s export/import feature rather than a native Atlassian migration path, we recommend planning the ID mapping step before your migration window.