daostack / daostack/common

Emails - No email to user when common is features

Open
#1,366 9 comments 0 reactions 0 assignees View on GitHub
bug low priority
Dominant language
TypeScript
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Tested on Staging iOS version 1.10.0(4)

Steps to reproduce:
1. As a user create a new common
2. As admin white list this common

Actual results:
No email to user when common is features

Expected results:
user who create this common should get email: (see below)

Subject: Your Common is now featured
Hello ,

The Common you created: , was selected to appear on the app’s “discover” section. Log in to find it there, and feel free to share the news with your fellow members.

For more information you can contact us any time using our support chat

Common,
Collaborative Social Action.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing the admin whitelist flow described in the reproduction steps and identify where the featured Common transition and email handling are implemented. Confirm the result against the requested subject, recipient, body, Common link, and support-chat link; done means the creator receives that email after whitelisting.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, typescript
Domain
backend, mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.