zulip/zulip-flutter

On profile page, handle is_imported_stub; update date_joined

Open

#2,201 opened on Mar 4, 2026

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Dart (456 forks)github user discovery
a-apihelp wantedserver-12

Repository metrics

Stars
 (454 stars)
PR merge metrics
 (PR metrics pending)

Description

See #api documentation > new feature level: 475:

  • GET /events: realm_user events with op: "update" are now sent when the date_joined field is updated after an imported stub user or a user created via the API logs in for the first time.
  • GET /users, GET /users/{user_id}, GET /users/{email}, GET /users/me: The date_joined field is initially set to the account creation time and is updated to the time of first login for imported stub users and users created via the API.

Tim elaborates that this means two changes for the mobile app:

  • Showing something to the effect of "Imported on" rather than "Date joined" as the string if is_imported_stub is true for a user whose card information is being displayed.
  • Being able to handle events that live-update is_imported_stub and date_joined if/when such a user joins in a way that converts the account from an imported stub into a real account.

and offers a tip for manually testing those changes (and producing screenshots):

There's a new "Imported user" account generated by populate_db that should make it easy to test with a Zulip development environment.

References

Contributor guide

Research direction
Investigate the current implementation of the profile page, specifically the user card display and the handling of user update events. Look for the 'is imported stub' field in the user model and the event handling for realm user events. Implement changes to show 'Imported on' when is imported stub is true, and handle the update event to update date joined and is imported stub.
Tech stack
dartflutter
Domain
mobile
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
FlutterDart
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70