Skip to content

[fix] Update end date field requirement based on event type#209

Merged
otc-zuul[bot] merged 3 commits into
mainfrom
i190
Jul 29, 2025
Merged

[fix] Update end date field requirement based on event type#209
otc-zuul[bot] merged 3 commits into
mainfrom
i190

Conversation

@Aloento
Copy link
Copy Markdown
Member

@Aloento Aloento commented Jul 21, 2025

Changes the requirement for the end date field in the event editor and new form to only be mandatory when the event type is Maintenance.

This improves user experience by ensuring that the field is conditionally required, preventing unnecessary errors for other event types.

Changes the requirement for the end date field in the event editor and new form to only be mandatory when the event type is Maintenance.

This improves user experience by ensuring that the field is conditionally required, preventing unnecessary errors for other event types.
@Aloento Aloento self-assigned this Jul 21, 2025
@Aloento Aloento linked an issue Jul 21, 2025 that may be closed by this pull request
@sgmv
Copy link
Copy Markdown
Contributor

sgmv commented Jul 21, 2025

Is blocked by stackmon/status-dashboard-v3#101

Copy link
Copy Markdown
Contributor

@sgmv sgmv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image

Unfortunately, it has a bug. The info event has 2 updates, but it shows only one with a wrong status.

@Aloento
Copy link
Copy Markdown
Member Author

Aloento commented Jul 23, 2025

PATCH /v2/incidents/608

image image

...can you help? Is 'active' not a valid status? @sgmv

Aloento added 2 commits July 23, 2025 11:02
# Conflicts:
#	src/Components/Event/EventEditor.tsx
Implements support for the Active status case in the TransformerV2 function.

This enhancement allows the system to correctly return the EventStatus.Active when dealing with active statuses, improving overall event handling.
@Aloento Aloento requested a review from sgmv July 23, 2025 09:03
@sgmv
Copy link
Copy Markdown
Contributor

sgmv commented Jul 24, 2025

image You still have a wrong status for the info event.

@Aloento
Copy link
Copy Markdown
Member Author

Aloento commented Jul 24, 2025

PATCH /v2/incidents/608

image image
...can you help? Is 'active' not a valid status? @sgmv

@sgmv can you?

@Aloento
Copy link
Copy Markdown
Member Author

Aloento commented Jul 28, 2025

image image

I didn't find any problems. If you look closely at the screenshot you provided, the planned status occurred after the active status (47 > 24), so it is correct that it is displayed as planned.

@sgmv
Copy link
Copy Markdown
Contributor

sgmv commented Jul 29, 2025

The bug relates to this issue #213

@Aloento Aloento added the gate Merge PR label Jul 29, 2025
@otc-zuul otc-zuul Bot merged commit a988c9c into main Jul 29, 2025
9 checks passed
@otc-zuul otc-zuul Bot deleted the i190 branch July 29, 2025 09:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gate Merge PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Optional end_date for the info event type

2 participants