All issues

Search results

Test Ladybug's security with the Frank!Framework

Status: Open.

#955 In wearefrank/ladybug;

· mhdirkse opened on Sep 4, 2026

Use pom <name> element in all poms and use similar names as all modules are connected

Status: Open.

#953 In wearefrank/ladybug;

· nielsm5 opened on Sep 3, 2026

In ladybug-backend-jaxrs, use @RolesAllowed instead of a separate authorization filter

Status: Open.

#951 In wearefrank/ladybug;

· mhdirkse opened on Sep 3, 2026

MessageContext mimetype field shows [object Object]

Status: Open.

#945 In wearefrank/ladybug;

· nielsm5 opened on Sep 2, 2026

Messagecontext field is not persistent

Status: Open.

#926 In wearefrank/ladybug;

· nielsm5 opened on Sep 1, 2026

Misleading toast message "Report rerun succesful"

Status: Open.

#923 In wearefrank/ladybug;

· jacodg opened on Aug 29, 2026

Webpage needed to do real releases of Ladybug

Status: Open.

#921 In wearefrank/ladybug;

· mhdirkse opened on Aug 28, 2026

Automate test of test-multi-instance-dropdown

Status: Open.

#918 In wearefrank/ladybug;

· mhdirkse opened on Aug 25, 2026

Improve org.wearefrank.ladybug.Rerunner.rerun() because to use argument of type SecurityContext wisely

Status: Open.

#913 In wearefrank/ladybug;

· mhdirkse opened on Aug 18, 2026

Let the build check or repair formatting of backend code

Status: Open.

#911 In wearefrank/ladybug;

· mhdirkse opened on Aug 13, 2026

Update README now that the Ladybug project is a monorepo

Status: Open.

#909 In wearefrank/ladybug;

· mhdirkse opened on Aug 13, 2026

Add toast when you rerun selected reports without anything selected

Status: Open.

#867 In wearefrank/ladybug;

· mhdirkse opened on Jul 14, 2026