-
Notifications
You must be signed in to change notification settings - Fork 848
OpenSep 16, 2026
Due by September 30, 2026
•Last updated 63% complete
List view
0 of 55 selected 0 issues of 55 selected
Make Legacy Saga code usable for migration purposes
Priority 1: MustHighest priority. A release cannot be made if this issue isn’t resolved.Highest priority. A release cannot be made if this issue isn’t resolved.Status: Open.#3728 In AxonIQ/AxonFramework;Move
EventSchedulertoaxon-legacyPriority 2: ShouldHigh priority. Ideally, these issues are part of the release they’re assigned to.High priority. Ideally, these issues are part of the release they’re assigned to.Status: Open.#3104 In AxonIQ/AxonFramework;Move Deadline support to
axon-legacyPriority 1: MustHighest priority. A release cannot be made if this issue isn’t resolved.Highest priority. A release cannot be made if this issue isn’t resolved.Status: Open.#3065 In AxonIQ/AxonFramework;Port
MongoTokenStoreandMongoSequencedDeadLetterQueuePriority 1: MustHighest priority. A release cannot be made if this issue isn’t resolved.Highest priority. A release cannot be made if this issue isn’t resolved.Status: Open.Projection Testing
Priority 2: ShouldHigh priority. Ideally, these issues are part of the release they’re assigned to.High priority. Ideally, these issues are part of the release they’re assigned to.Type: FeatureUse to signal an issue is completely new to the project.Use to signal an issue is completely new to the project.Status: Open.#729 In AxonIQ/AxonFramework;Introduce
TargetContextResolverdecorator aroundCommandBusConnectorPriority 2: ShouldHigh priority. Ideally, these issues are part of the release they’re assigned to.High priority. Ideally, these issues are part of the release they’re assigned to.Status: Open.Introduce "version selector" support for Message Handler Registries
Priority 2: ShouldHigh priority. Ideally, these issues are part of the release they’re assigned to.High priority. Ideally, these issues are part of the release they’re assigned to.Status: Open.React on
FirstTrackingTokenandLatestTrackingTokenPriority 2: ShouldHigh priority. Ideally, these issues are part of the release they’re assigned to.High priority. Ideally, these issues are part of the release they’re assigned to.Status: Open.AxonTestFixture: Automatic event processor catch-up at phase transitionsPriority 2: ShouldHigh priority. Ideally, these issues are part of the release they’re assigned to.High priority. Ideally, these issues are part of the release they’re assigned to.Status: Open.#4252 In AxonIQ/AxonFramework;Port, align, and optimize Spring Cloud Extension
Priority 1: MustHighest priority. A release cannot be made if this issue isn’t resolved.Highest priority. A release cannot be made if this issue isn’t resolved.Status: Open.Allow QueryUpdateEmitter filters to conveniently access converted payloads
Priority 3: CouldLow priority. Issues that are nice to have but have a straightforward workaround.Low priority. Issues that are nice to have but have a straightforward workaround.Status: Open.#4328 In AxonIQ/AxonFramework;Ensure alignment between command chapter flow with event chapter flow
Priority 3: CouldLow priority. Issues that are nice to have but have a straightforward workaround.Low priority. Issues that are nice to have but have a straightforward workaround.Status: Open.#4057 In AxonIQ/AxonFramework;Support Query Results with several layers of generics
Priority 3: CouldLow priority. Issues that are nice to have but have a straightforward workaround.Low priority. Issues that are nice to have but have a straightforward workaround.Status: Open.Describe the role of the
UnitOfWorkFactoryPriority 4: WouldLowest priority. Would-be-nice to include issues when time allows it.Lowest priority. Would-be-nice to include issues when time allows it.Status: Open.#4061 In AxonIQ/AxonFramework;Spring Context can not be created when AxonTimeoutAutoConfiguration is active
Priority 2: ShouldHigh priority. Ideally, these issues are part of the release they’re assigned to.High priority. Ideally, these issues are part of the release they’re assigned to.Type: BugUse to signal issues that describe a bug within the system.Use to signal issues that describe a bug within the system.Status: Open.#3959 In AxonIQ/AxonFramework;Ensure alignment between query chapter flow with event chapter flow
Priority 3: CouldLow priority. Issues that are nice to have but have a straightforward workaround.Low priority. Issues that are nice to have but have a straightforward workaround.Status: Open.#4058 In AxonIQ/AxonFramework;The RetryScheduler on the query bus/gateway
Priority 3: CouldLow priority. Issues that are nice to have but have a straightforward workaround.Low priority. Issues that are nice to have but have a straightforward workaround.Type: EnhancementUse to signal an issue enhances an already existing feature of the project.Use to signal an issue enhances an already existing feature of the project.Status: Open.#1692 In AxonIQ/AxonFramework;ReactiveSecurityContextHolder is empty inside @QueryHandler in Spring WebFlux applications
Priority 3: CouldLow priority. Issues that are nice to have but have a straightforward workaround.Low priority. Issues that are nice to have but have a straightforward workaround.Status: Open.Automated message handler registration with multiple
QualifiedNamesPriority 2: ShouldHigh priority. Ideally, these issues are part of the release they’re assigned to.High priority. Ideally, these issues are part of the release they’re assigned to.Status: Open.#3783 In AxonIQ/AxonFramework;Define strategy for Message Handling Components when several handlers for same
QualifiedNameare subscribedPriority 2: ShouldHigh priority. Ideally, these issues are part of the release they’re assigned to.High priority. Ideally, these issues are part of the release they’re assigned to.Status: Open.#3733 In AxonIQ/AxonFramework;Allow handling events that are part of a sealed event hierarchy
Priority 2: ShouldHigh priority. Ideally, these issues are part of the release they’re assigned to.High priority. Ideally, these issues are part of the release they’re assigned to.Status: DuplicateUse to signal this issue is a duplicate of another. Please refer to the other issue.Use to signal this issue is a duplicate of another. Please refer to the other issue.Status: Open.Reject or warn about wrong usage of
@EventHandlerand@EventSourcedHandlerannotationsPriority 4: WouldLowest priority. Would-be-nice to include issues when time allows it.Lowest priority. Would-be-nice to include issues when time allows it.Type: EnhancementUse to signal an issue enhances an already existing feature of the project.Use to signal an issue enhances an already existing feature of the project.Status: Open.#1755 In AxonIQ/AxonFramework;feat(eventsourcing): add
@AppendCriteriaBuilder- enables different EventCritera for sourcing (loading events) and appending (consistency checking)Priority 1: MustHighest priority. A release cannot be made if this issue isn’t resolved.Highest priority. A release cannot be made if this issue isn’t resolved.Type: FeatureUse to signal an issue is completely new to the project.Use to signal an issue is completely new to the project.Status: Open (in progress).AxonIQ/AxonFrameworknumber 4125#4125 In AxonIQ/AxonFramework;Adjust
EntityMetamodel#CREATE_WITHOUT_LOADusagePriority 2: ShouldHigh priority. Ideally, these issues are part of the release they’re assigned to.High priority. Ideally, these issues are part of the release they’re assigned to.Status: Open.#4588 In AxonIQ/AxonFramework;Fail fast when
SpringComponentRegistrycomponents are queried before promotionPriority 3: CouldLow priority. Issues that are nice to have but have a straightforward workaround.Low priority. Issues that are nice to have but have a straightforward workaround.Status: Open.#4726 In AxonIQ/AxonFramework;