Skip to content

Backend API updates#5047

Open
NPS-ESR wants to merge 4 commits intoushahidi:developfrom
NPS-ESR:develop
Open

Backend API updates#5047
NPS-ESR wants to merge 4 commits intoushahidi:developfrom
NPS-ESR:develop

Conversation

@NPS-ESR
Copy link
Copy Markdown

@NPS-ESR NPS-ESR commented Mar 19, 2026

This pull request makes the following changes:

  • Enforce role-based survey visibility for users API changes
  • Post Ownership Reassignment on Update API changes
  • Sort by Event Date filter API changes
  • Move Post to Survey API changes
  • Unread Posts API Endpoint

Test checklist:

  • [ ]

  • I certify that I ran my checklist

Fixes ushahidi/platform# .

Ping @ushahidi/platform

NPS-ESR added 4 commits March 19, 2026 20:16
… work with the surveys assigned to their role. Since users have different responsibilities, showing all surveys to everyone can be confusing and may expose data they shouldn’t access. Limiting visibility will help keep things clear and ensure users only interact with the surveys relevant to them.
…name, and author_email fields are either pulled from the incoming request or retained from the original post. This behavior needs to be revised so that ownership of the post is reassigned to the user performing the update.

By doing this, any user who updates a post becomes the recognized owner of that update. This change is important for maintaining accurate audit trails, ensuring proper ownership in multi-user environments, and keeping post metadata (such as real name and email) aligned with the individual who most recently modified or published the content—regardless of the original creator.
… by the most relevant date for a report (either a custom user-provided date or the system-recorded date) the custom-user-provided date is sometimes used by clients fo flag a possible event in the future with this sort we can now list the possible future events.
…d data management efficiency within the Ushahidi platform. In complex deployments, reports are frequently submitted to the wrong campaign or require reclassification as project structures evolve. Previously, correcting these misplacements required tedious manual data entry. By providing a native Move capability, users can quickly rectify filing errors, consolidate data across campaigns, and ensure that reports are always associated with the correct set of fields and workflows without losing the original post's history or metadata.
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.

1 participant