ietf-tools / ietf-tools/datatracker

Improve the representation of whether mail was sent when a DISCUSS or COMMENT was changed

Open
#6,830 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

accepted component: Datatracker: Email sending enhancement minor
Dominant language
Python
Stars
1.1k
Forks
853
Avg merge
1d 4h
Merged PRs (30d)
45

Description

On the IESG evaluation page, each DISCUSS/COMMENT shows a 'Sent' (green) or 'Not sent' (red) email icon, but these labels contradict their tooltips ('Email requested to be sent' / 'No email send requests'), making them unintuitive (#6830). Requests relabeling the icons (e.g. 'Requested' / 'Not Requested') to match intent, and making the icon hyperlink to a pre-populated mailto to the AD with appropriate CCs.

Tasks
  • Relabel the DISCUSS/COMMENT email-status icons to match their tooltip meaning
  • Make the email-status icon link to a pre-populated mailto to the AD with CCs

Agent-assisted triage

  • Suggested size: S
  • Suggested priority: minor
  • Suggested lane: standard
  • Analysis confidence: medium
  • Updated with agent assistance on 2026-08-21

Original report

From Stephan Wenger:

On the IESG evaluation page of the datatracker, in the headline of each COMMENT or DISCUSS, there’s an email icon that says “Not sent” in red, or “Sent” in green. The mouse-overs of these icons say “No email send requests for this comment” and “Email requested to be send for this comment”, respectively. I believe that the mouse-overs reflect the intention, but the labeling of the icons do not; they are unintuitive. May I suggest to rename the green” Sent” item to “ Requested” and the red “ Not sent” to “ not Requested” or “ not Required”.

I would also suggest that the icons hyperlink to a mailto: to the AD requesting a response, with appropriate CCs pre-populated if possible.

Contributor guide

Open the contributing guide

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.

Research direction

Start at the IESG evaluation page and inspect how DISCUSS and COMMENT email-status icons are rendered. Update the labels to match their tooltip meaning and make the icons produce a pre-populated mailto to the AD with appropriate CCs; verify both sent-request states.

Written by the indexing model from the issue text.

Assessment

Tech stack
django, python
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.