Jira - OpenText Core Digital Asset Management Integration and Automation

Common Integration Use Cases Between Jira and OpenText Core Digital Asset Management

Jira and OpenText Core Digital Asset Management complement each other well in organizations that manage digital content alongside structured work delivery. Jira provides the workflow, task tracking, and cross-team coordination needed to execute projects, while OpenText Core Digital Asset Management serves as the controlled repository for approved images, videos, brand assets, and other digital files. Integrating the two platforms helps teams connect work execution with governed asset management, improving speed, traceability, and collaboration.

1. Creative Asset Request and Approval Workflow

Marketing, product, or internal communications teams can create Jira issues to request new digital assets such as campaign images, product screenshots, or training videos. Once the request is approved and completed, the final asset is uploaded to OpenText Core Digital Asset Management and linked back to the Jira ticket for traceability.

• Direction: Jira to OpenText Core Digital Asset Management
• Business value: Reduces email-based requests, improves visibility into asset status, and ensures only approved files are stored in the DAM
• Example: A campaign manager submits a Jira request for a banner set, and the completed files are published to the DAM with the Jira issue updated automatically

2. Centralized Access to Approved Assets from Jira Work Items

Teams working in Jira can access approved brand assets, templates, and reference files stored in OpenText Core Digital Asset Management directly from issues, epics, or project pages. This helps designers, developers, and content teams use the correct version without searching across shared drives or email threads.

• Direction: OpenText Core Digital Asset Management to Jira
• Business value: Improves productivity, reduces version confusion, and supports brand compliance
• Example: A Jira story for a website refresh includes a link to the approved logo set and product imagery stored in the DAM

3. Asset Review and Revision Tracking

When a digital asset needs revision, a Jira issue can be created automatically from the DAM workflow or manually by a content manager. The Jira ticket tracks review comments, required changes, and approval steps, while the DAM retains the final approved version and metadata.

• Direction: Bi-directional
• Business value: Creates a controlled review process and provides auditability for regulated or brand-sensitive content
• Example: A product brochure in the DAM is flagged for update, and Jira tracks the revision tasks assigned to design, legal, and product teams

4. Release Readiness for Product and Campaign Launches

Jira can be used to manage launch tasks, dependencies, and release milestones, while OpenText Core Digital Asset Management stores the final launch assets such as product images, launch videos, sales decks, and localized content. Integration ensures that launch tasks in Jira are linked to the correct approved assets in the DAM.

• Direction: Bi-directional
• Business value: Aligns content readiness with project delivery and reduces launch delays caused by missing assets
• Example: A Jira release checklist includes links to the final approved assets required for a product launch across web, sales, and partner channels

5. Localization and Regional Content Coordination

Global organizations can use Jira to manage localization tasks for different regions and languages, while OpenText Core Digital Asset Management stores localized versions of approved assets. Jira issues can track translation, adaptation, and regional approval steps, with the DAM serving as the source of truth for published content.

• Direction: Bi-directional
• Business value: Improves coordination across regional teams and ensures consistent use of localized content
• Example: A global campaign epic in Jira contains subtasks for French, German, and Japanese asset versions, each linked to the corresponding files in the DAM

6. Compliance and Audit Support for Controlled Assets

For industries with strict governance requirements, Jira can track review and approval tasks for assets that require legal, regulatory, or brand compliance checks. OpenText Core Digital Asset Management stores the approved final assets and associated metadata, while Jira provides the workflow history showing who reviewed and approved each item.

• Direction: Jira to OpenText Core Digital Asset Management
• Business value: Strengthens audit readiness and supports controlled content governance
• Example: A healthcare marketing asset is routed through Jira for compliance review before the approved version is published in the DAM

7. Operational Handoff Between Development and Content Teams

Development teams using Jira often need approved screenshots, icons, illustrations, or UI assets from content or design teams. Integration allows developers to reference the latest approved files in OpenText Core Digital Asset Management directly from Jira stories and bugs, reducing rework and miscommunication.

• Direction: OpenText Core Digital Asset Management to Jira
• Business value: Speeds up delivery, reduces defects caused by outdated assets, and improves collaboration between technical and creative teams
• Example: A Jira bug for a mobile app update includes a link to the approved icon set and app store graphics stored in the DAM

Overall, integrating Jira with OpenText Core Digital Asset Management helps organizations connect work management with governed asset delivery. The result is better visibility, faster approvals, stronger compliance, and more efficient collaboration across marketing, product, design, and development teams.