# How to Create Jira Tickets from Cost Recommendations: Step by Step

> How to Create Jira Tickets from Cost Recommendations. A practical walkthrough with ZopNight: read-only setup, production excluded by default, reversible at every step.

Source: https://zop.dev/learn/how-to/create-jira-tickets-from-recommendations
Published: 2026-07-01 · Author: avinash-gaurav · Tags: zopnight, how-to, learn

---

Step-by-step guide to connecting Jira to ZopNight and opening tickets from cost recommendations, with optional policy-driven auto-ticketing and two-way status sync.

This is the practical version, the one you can follow in a single sitting. It starts read-only, touches no production resource by default, and every step is reversible, so there is no point at which you are committed to something you cannot undo. Budget about 15 minutes. Before you start you will want: A Jira project and API token; Admin access to Settings then Integrations.

## The steps

1. Connect Jira.
2. Open a ticket from a recommendation.
3. Set a policy for auto-ticketing.
4. Let status and ownership stay in sync.

## Why this is safe to do today

The reason this is a low-stakes change is that nothing here is destructive. Scheduling stops and starts resources; it never deletes them, and your data persists across a stop exactly as it does across a normal reboot. Production is excluded by default, actions run in dependency order, and every state change is logged with what triggered it.

If you want the fuller context behind this task, the [FinOps](https://zop.dev/learn/finops) guide covers where it fits, and the [AWS EC2 scheduling](https://zop.dev/zopnight/aws/ec2) page shows the same loop applied to a specific resource.

## Getting started

Getting started is intentionally low-stakes:

- Connect your cloud provider with a read-only role. Nothing is scheduled or changed at this stage.
- Let ZopNight discover your non-production resources and review exactly what it found, filtered by account, region, and status.
- Create a schedule in your timezone and attach the non-production resources or groups you want it to cover.
- Watch the first cycle run, with Slack, Teams, or Google Chat notifications on every start, stop, and failure, then layer in idle cleanup and guided rightsizing.

Production stays excluded by default throughout, and because discovery and recommendations are read-only, you can prove the value before you enable a single action.

## Frequently asked questions

### Will I get duplicate tickets?

No. Dedup is keyed on a stable fingerprint over the organisation, resource, and rule type, so a repeated request is a no-op.

### Does status sync both ways?

Yes. Recommendation and Jira issue statuses stay in agreement automatically, event-driven, with a loop guard to prevent ping-pong.