feat: [DHIS2-21875] Unify overflow menu between View Event page and Stages and Events widget

[henrikmv]

DHIS2-21875

Verification matrix by event status

Baseline: user has canEditProgramStage. Without it, no mutation actions appear at all (overflow menu section hidden).

Event status	Edit form	Complete/Uncomplete button	Skip/Unskip menu item	Delete menu item
ACTIVE	Editable if not expired ¹	Complete — enabled if not expired ¹	Hidden	Enabled if not expired ¹
COMPLETED (blockEntryForm=false)	Editable if not expired ¹	Uncomplete — enabled when user has F_UNCOMPLETE_EVENT AND (not expired OR has F_EDIT_EXPIRED)	Hidden	Enabled if not expired ¹
COMPLETED (blockEntryForm=true)	Read-only — badge "This event has been completed"; must Uncomplete first	Uncomplete — enabled when user has F_UNCOMPLETE_EVENT AND (not expired OR has F_EDIT_EXPIRED)	Hidden	Enabled if not expired ¹
SCHEDULE	Editable — user picks a valid occurredAt ²	Hidden	Skip — enabled if not expired ¹	Enabled if not expired ¹
OVERDUE	Editable — user picks a valid occurredAt ²	Hidden	Skip — enabled if not expired ³	Enabled if not expired ³
SKIPPED	Read-only — event is skipped	Hidden	Unskip — enabled if not expired ¹	Enabled if not expired ¹

Additonal information

¹ Expiry rules

"Not expired" means the event's relevant date is inside the program's editing window:

• occurredAt for ACTIVE / COMPLETED
• scheduledAt for SCHEDULE / OVERDUE / SKIPPED

F_EDIT_EXPIRED bypasses expiry checks. However, it does not bypass other permission requirements. For example, Uncomplete still requires F_UNCOMPLETE_EVENT.

² SCHEDULE / OVERDUE edit exception

For SCHEDULE and OVERDUE, form editing checks expiry against the date currently entered in the form rather than the server-side date.

This means a user without F_EDIT_EXPIRED can still save the event by selecting a valid date inside the editing window.

³ Skip / Delete on OVERDUE

Skip and Delete continue to check the server-side scheduledAt.

If scheduledAt is outside the editing window, both actions remain disabled unless the user has F_EDIT_EXPIRED.

Completed events with blockEntryForm=true

When an event is COMPLETED and blockEntryForm=true, the form is read-only. To edit the event, you have to Uncomplete — requires F_UNCOMPLETE_EVENT.

If the event is expired, Uncomplete also requires F_EDIT_EXPIRED.

Overflow menu visibility

Action	Visible for
Skip / Unskip	SCHEDULE, SKIPPED, OVERDUE
Complete / Uncomplete	ACTIVE, COMPLETED
Delete	All statuses

[github-actions]

🚀 Deployed on https://deploy-preview-4657.capture.netlify.dhis2.org

[simonadomnisoru]

Looks good! I just added a comment for a follow-up ticket so we don't forget about that use case.

[simonadomnisoru]

It looks like the Mark complete action in the Overflow menu isn't considering the askCompleteEnrollmentOnEventComplete flag right now. (Since it was added in PR #4649, perhaps this comment would have been better suited there 🤔 ). We can handle the flag in a follow-up ticket 😄 .

[henrikmv]

I did not know about that feature. It has been implemented in #4649 now. Thanks!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud