[FEATURE] Add statistics by email and by tags

Open
  • Is something wrong?
#305 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
analytics

Research direction

Start by reading the search page and dashboard implementations to identify how their filters and message statistics are built, then inspect the API entry points that expose dashboard data. The issue calls for a new statistics page and corresponding API, including tag counts by period and message direction; done means those views and metrics are available, though the required aggregation and API details need design decisions.

Written by the indexing model from the issue text.

Description

enhancement
Description

Add a new menu between the search and attachments options to display message volume statistics.

The first part of the page could replicate the filters from the search page (to maintain a consistent display).
The second part would present the same information as the dashboard, namely: number of messages, number of attachments, a graph of new messages, and top senders.
Provide a corresponding API

Purpose / Use Case

Certain metrics related to the volume of messages sent or received can be relevant.

For example, the number of messages sent to customer support, complaints, quote requests, etc. Therefore, it would be useful to have the ability to generate statistics on tags in the form of a table with the defined tags in rows, the period (week, month, quarter, year) in columns, and the number of emails (sent, received, all) in the values.

Additional Information (optional)

Any extra ideas or context.

Dominant language
Rust
Stars
2.1k
Forks
91
Avg merge
14h 54m
Merged PRs (30d)
6

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rustmailer/bichon

All issues in rustmailer/bichon

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.