Skip to main content
← All updates
Changelog

Jira Ticket Sync & Software Contracts Polish


This week brings two-way Jira ticket sync into June, surfaces linked tickets on asset and employee pages, and rounds out the software contracts experience with a new Expiring Soon view and an admin product catalog.

Product Improvements
  • Jira Ticket Sync via Webhooks: Jira tickets from tracked projects now upsert into June automatically, with reporter and device links resolved on the fly so every ticket is connected to the right people and hardware.
  • Internal Context Comments on New Jira Tickets: When a new Jira ticket lands, June posts an internal comment with the reporter’s profile and assigned devices so IT teammates have the full picture before they start triaging.
  • Tickets Tab on Asset & Employee Pages: Asset and employee detail pages now include a Tickets tab that lists linked ITSM tickets with search, count badges, and lazy loading.
  • Expiring Soon Contracts Tab: The Software Contracts page picks up an Expiring Soon tab and full status counts on every tab badge to make renewal triage faster.
  • Needs Matching & Link-to-Application: A new Needs Matching tab groups unmapped contracts together, with a link-to-application popover for attaching them to the right software product in one click.
  • Compact Contract Form with Inline Document Preview: The contract form is tighter and faster to scan, and the documents list now previews PDFs and images inline instead of forcing a download.
  • Zip Sync Enrichment: Improved vendor and document matching during Zip syncs so contracts pull in cleaner product, vendor, department, and category data on first try.
Bug Fixes
  • Accurate Contract Length: Contract length now uses month-based math and correctly clears the end date for perpetual contracts.
  • Contract Form Stability: Resolved errors and stale data that could appear when editing contracts back-to-back.
  • Tickets Tab Resilience: Cached ticket data now persists across transient network errors instead of flashing an empty state.
  • License Count Handling: Explicit zero license counts are preserved on save and the field is properly optional throughout the contract form.

Ready to put IT on autopilot?

Talk to an expert