Skip to content

[ENG-11457] require at least 1 subject for draft and usual registrations#11786

Open
ihorsokhanexoft wants to merge 26 commits into
CenterForOpenScience:feature/pbs-26-13from
ihorsokhanexoft:fix/ENG-11457
Open

[ENG-11457] require at least 1 subject for draft and usual registrations#11786
ihorsokhanexoft wants to merge 26 commits into
CenterForOpenScience:feature/pbs-26-13from
ihorsokhanexoft:fix/ENG-11457

Conversation

@ihorsokhanexoft

Copy link
Copy Markdown
Contributor

Ticket

https://openscience.atlassian.net/browse/ENG-11457

Purpose

Draft registrations and usual registration should have at least 1 subject

Changes

Added validation

mkovalua and others added 26 commits April 23, 2026 18:16
…NG-10768

* https://openscience.atlassian.net/browse/ENG-10768

## Purpose

When OSF undergoes planned downtime for software releases, users who are unaware of the maintenance window have no way of knowing the site is intentionally offline — they simply experience a broken site. A backend maintenance mode is needed so that when enabled, the API halts normal request processing and signals to clients that the system is in maintenance.

## Changes

return 503 for API if maintanence_mode is set to true

set maintenance mode via admin
… and selective existing templates (CenterForOpenScience#11698)

* Add options to sync notification templates: restore one or all
* Fix formatting of template name input in management commands
…nd improve template preview (CenterForOpenScience#11715)

* Refactor notifications admin interface: add views, templates, and URLs for notifications management
* Refactor notification rendering: enhance error handling and add mock data support in preview
* Add JSON parsing error
…tionDetail' updates response (CenterForOpenScience#11719)

* Add the 'id' and 'event_name' attributes to the 'SubscriptionDetail' updates response
* Add assertions for 'id' and 'event_name' in subscription detail response test
…ce/develop

Merge develop into feature/pbs-26-9
…erge-develop

[ENG-11259] Merge `develop` into `pbs-26-9` and fix migrations
…tivity logs (CenterForOpenScience#11697)

* expose foreign_user in logs response; add missing logs for admin actions
* fix tests
* minor fixes; add tests
Conflicts not fixed in admin_tests/nodes/test_views.py
…update digest email tasks (CenterForOpenScience#11764)

* Add scheduled field to Notification model and update digest email tasks
* Fix scheduled field handling in email tasks and update migration

@sh-andriy sh-andriy left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM. Validation's in the right spot (register + both set_subjects paths) and the relationship endpoint is replace-only so there's no DELETE bypass. Error maps to a clean 400. Approving.

@brianjgeiger brianjgeiger changed the base branch from feature/pbs-26-9 to feature/pbs-26-13 June 26, 2026 14:38
@brianjgeiger

Copy link
Copy Markdown
Collaborator

@ihorsokhanexoft Please rebase onto feature/pbs-26-13 to get rid of the extra commits from feature/pbs-26-9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants