Jira - OpenText TeamSite - LiveSite Content Services Integration and Automation

Common Integration Use Cases Between Jira and OpenText TeamSite - LiveSite Content Services

1. Marketing and digital experience change requests tracked in Jira and published through LiveSite

Data flow: Jira ? OpenText TeamSite - LiveSite Content Services

Business teams can log website content changes, landing page updates, and personalization requests in Jira, where they are reviewed, prioritized, and assigned to content or web operations teams. Once approved, the implementation team updates and publishes the content in LiveSite.

• Improves visibility into content demand and delivery status
• Creates a controlled workflow for web changes
• Reduces missed requests and ad hoc email-based coordination

2. Content publishing tasks linked to release management in Jira

Data flow: Bi-directional

When a new digital experience release is planned in Jira, related content updates in LiveSite can be linked to the same release epic or sprint. Publishing tasks, approvals, and deployment checkpoints can be synchronized so content goes live with the application release.

• Aligns content deployment with product release schedules
• Reduces risk of publishing outdated or incomplete content
• Supports coordinated launches across development, QA, and content teams

3. Defect and content issue management for customer-facing portals

Data flow: OpenText TeamSite - LiveSite Content Services ? Jira

If a broken page, incorrect personalization rule, or missing content element is detected in LiveSite, an issue can be automatically created in Jira for triage and resolution. This is especially useful for customer portals, self-service sites, and campaign pages where content defects affect user experience and conversion.

• Speeds up incident logging and assignment
• Provides traceability from customer-facing issue to resolution
• Helps teams prioritize issues based on business impact

4. Approval workflow for regulated or high-risk content

Data flow: Bi-directional

For industries such as financial services, healthcare, or public sector, content changes in LiveSite can require formal review and approval. Jira can manage the approval workflow, track reviewers, and maintain an audit trail before content is published.

• Supports compliance and governance requirements
• Ensures accountability for content sign-off
• Provides a documented approval history for audits

5. Personalization rule enhancement requests from product and analytics teams

Data flow: Jira ? OpenText TeamSite - LiveSite Content Services

Product managers or analytics teams can submit Jira stories for new personalization rules, audience segments, or contextual content variations. The web team then implements the logic in LiveSite to improve relevance for different customer groups.

• Turns analytics insights into actionable content improvements
• Creates a structured backlog for personalization enhancements
• Improves conversion and engagement through targeted experiences

6. Content operations reporting tied to Jira delivery metrics

Data flow: Bi-directional

Jira issue status can be combined with LiveSite publishing data to measure content delivery performance, such as average request turnaround time, approval cycle duration, and on-time launch rates. This gives managers a clearer view of operational efficiency across content and digital teams.

• Enables SLA tracking for content operations
• Identifies bottlenecks in review, development, or publishing
• Supports continuous improvement in digital delivery processes

7. Cross-team coordination for campaign launches and portal updates

Data flow: Bi-directional

For major campaigns or portal updates, Jira can serve as the central coordination hub for development, QA, legal, and content teams, while LiveSite handles the final content delivery. Tasks, dependencies, and launch readiness can be tracked in Jira, with publishing status reflected back to stakeholders.

• Reduces launch delays caused by poor coordination
• Improves transparency across business and technical teams
• Supports repeatable launch processes for recurring campaigns