[changelog] [Announcement] Confluence content property module can now be declared as a dynamic module (Preview)

Open
#14 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
typescript
Domain
tooling

Research direction

Start in the manifest/modules simulator area and compare its handling of jira:entityProperty with the Forge Dynamic Modules API documentation linked in the issue. Determine whether dynamic module simulation already exists; done means either confluence:contentProperty is accepted as a dynamic module type alongside Jira entity properties, or the missing simulation scope is clearly recorded for future work.

Written by the indexing model from the issue text.

Description

upstream-changelog

GUID: CHANGE-3367
pubDate: Mon, 27 Jul 2026 00:16:33 GMT
Category: Announcement

What's changing

The confluence:contentProperty module can now be registered dynamically at runtime, per installation, via the Forge Dynamic Modules API (Preview). This brings the same dynamic registration capability already available for Jira entity properties (jira:entityProperty) to the Confluence side.

Parity impact for forge-sim

Simulator area: manifest/modules.

  • If forge-sim models the dynamic modules API for jira:entityProperty, confluence:contentProperty should be accepted as a dynamically registrable module type too.
  • If dynamic modules aren't simulated yet, this is a data point that the surface is growing (now spans Jira + Confluence module types) — worth tracking for a future dynamic-modules simulation surface.
  • Static manifest declaration of confluence:contentProperty is unchanged; this is additive.

Docs: https://developer.atlassian.com/platform/forge/apis-reference/dynamic-modules/
Link: https://developer.atlassian.com/platform/forge/changelog/#CHANGE-3367

Dominant language
TypeScript
Stars
5
Forks
2
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ryanackley/forge-sim

All issues in ryanackley/forge-sim

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.