OpenText DAM (OTMM) - Jira Integration and Automation

Common Integration Use Cases Between OpenText DAM (OTMM) and Jira

1. Marketing asset request and approval workflow

Direction: Jira to OpenText DAM (OTMM), with status updates back to Jira

Marketing teams can create Jira requests for new campaign images, videos, or product visuals. Once approved, the request is routed to OpenText DAM (OTMM) for asset creation, tagging, and storage. DAM completion status, asset links, and approval outcomes are then pushed back into Jira so stakeholders can track progress without leaving the project board.

• Reduces email-based follow-up and manual status checks
• Improves visibility for marketing, creative, and brand teams
• Ensures only approved assets move into campaign execution

2. Product image defect and correction management

Direction: OpenText DAM (OTMM) to Jira

When product images in the DAM are found to be outdated, incorrectly labeled, or non-compliant with brand standards, OTMM can automatically create Jira issues for the responsible content or product team. Each issue can include the asset ID, preview, metadata, and reason for correction, enabling fast remediation and traceability.

• Speeds up correction of inaccurate product visuals
• Creates a clear audit trail for content quality issues
• Helps product and marketing teams prioritize fixes by severity

3. Campaign asset production tracking

Direction: Bi-directional

For large campaigns, Jira can manage the work breakdown structure for asset production, including design, editing, localization, and review tasks. OpenText DAM (OTMM) stores the final approved images and videos, while Jira tracks the production workflow. Asset metadata, approval status, and version references can sync between systems to keep campaign teams aligned.

• Supports end-to-end campaign delivery tracking
• Prevents use of outdated or unapproved creative files
• Improves coordination across creative, legal, and marketing operations

4. Release readiness for product content and media

Direction: Jira to OpenText DAM (OTMM)

When a product release is approaching, Jira can trigger tasks for finalizing associated media such as product photos, demo videos, and launch banners. Once the release task is completed, OTMM can receive the approved asset package and publish it to downstream distribution channels. This ensures product content is ready in sync with software or product launches.

• Aligns media readiness with product release schedules
• Reduces launch delays caused by missing assets
• Supports coordinated go-to-market execution

5. Museum and heritage collection digitization workflow

Direction: Jira to OpenText DAM (OTMM), with asset references returned to Jira

Museums and heritage organizations can use Jira to manage digitization projects for collections, including photography, video capture, metadata enrichment, and review. OpenText DAM (OTMM) stores the digitized media and associated descriptive information. Jira tracks each collection item as a work item, while OTMM provides the authoritative media repository and access links.

• Improves control over large-scale digitization programs
• Provides traceability for collection item processing
• Supports collaboration between curators, archivists, and media teams

6. Bug tracking for DAM content and workflow issues

Direction: OpenText DAM (OTMM) to Jira

If users encounter issues in OTMM such as broken renditions, failed uploads, incorrect metadata mapping, or publishing errors, the DAM can create Jira bugs or service tickets automatically. This gives IT and platform teams a structured intake process for resolving operational issues and tracking root causes.

• Improves support response time for DAM users
• Centralizes issue management for platform operations
• Helps identify recurring integration or content processing failures

7. Asset localization and channel distribution coordination

Direction: Bi-directional

For organizations distributing product images and videos across multiple regions or channels, Jira can manage localization tasks such as translation, cropping, format conversion, and channel-specific review. OpenText DAM (OTMM) stores the approved localized versions and distributes them to downstream systems. Jira receives completion updates and can trigger follow-up tasks if a channel rejects an asset.

• Supports multi-channel and multi-market content operations
• Reduces errors in localized asset delivery
• Improves accountability across regional teams and channel owners

8. Event media production and post-event content management

Direction: Jira to OpenText DAM (OTMM)

For marketing and company events, Jira can manage the production workflow for event photography, highlight reels, speaker clips, and promotional edits. Once assets are approved, they are stored in OpenText DAM (OTMM) with proper metadata and usage rights. This makes it easier for teams to reuse event media in future campaigns, internal communications, and social distribution.

• Streamlines event content production and approval
• Improves reuse of approved media assets
• Ensures rights and metadata are captured before distribution