U
member badge
Uday Korlimarla
Port’s current Jira integration supports syncing Projects, Issues, Users, and Teams, but does not support additional Jira Agile entities such as Sprints, Boards, Epics, Worklogs, Backlog items, Versions, or other objects available through the Jira Cloud Agile REST API.
These objects are essential for richer engineering insights, cross-team reporting, and end-to-end service catalog modeling.
Adding support for these Jira resource types would unlock significantly more powerful catalog and automation use cases for Port customers.
Primary targets:
  • Sprint
  • Board
  • Epic (as its own blueprint)
  • Worklog
  • Version / Release
Nice to have:
  • Backlog containers
  • Components
  • Iterations for Jira Advanced Roadmaps
Technical expectations
  • Read support through the Jira Cloud Agile REST API
  • Ability to map fields using Port’s mapping layer (JQ)
Relations:
  • Sprint → Issues
  • Board → Sprints
  • Epic → Issues
  • Version → Deployments / Releases / Services
Additionally: live events for sprint changes (start/end), board updates, and linked issues.