File Jira tickets from recommendations; policy-driven tags.
Jira ticketing and Smart Tags
ZopNight now files Jira tickets straight from your cost recommendations — by hand or by policy — with two-way status sync. And Smart Tags replaces the old heuristic auto-tagger with virtual tags derived only from the tagging policies you define, used for cost attribution and never written back to your cloud.
What's in this release
- New ZopNight: file Jira tickets straight from cost recommendations — connect Jira in Settings ▸ Integrations (classic or scoped tokens), file by hand or set a policy (e.g. a ticket for every idle resource over $50/mo). Each ticket carries the resource, savings, and suggested fix with a link back, status stays in two-way sync, and re-running never files a duplicate
- New ZopNight: Smart Tags — virtual tags derived only from tagging policies you define (a new Tagging domain on the Policy page), used for cost attribution and never written back to your cloud, with a Smart Tags page to review and accept or revoke derived tags in bulk or per resource (replaces the old heuristic auto-tagger)