You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the IESG evaluation tab, each ballot position should link to the associated discussion email in the mail archive so the responsible AD can follow up. Linking to the exact message via Archived-At is impractical (Datatracker cannot compute it before the mail pipeline runs); the agreed ~95% solution is a canned mail-archive subject search link, placed on the "email requested to send" envelope icon or the Discuss/Comment header text. See #4387.
Task
Add a canned mail-archive subject-search link to each ballot position in the IESG evaluation tab
Agent-assisted triage
Suggested size: M
Suggested priority: medium
Suggested lane: needs-decision
Analysis confidence: medium
Updated with agent assistance on 2026-08-21
Original report
Description
When looking through the IESG evaluation tab of an internet-draft, it would be useful if each ballot position linked directly to the associated email in the archive. As a responsible AD, it would make it much easier for me to see the result of any discussion that followed the ballot.
When I first read this, my reaction was that it's a pretty big ask. (Almost) anything is possible, of course, but this would require some interesting machinery, assuming what you mean is to link to the exact message using the Archived-At header for messages that have made it into the archive.
But thinking for a moment, if you mean, instead, a canned search that would match any messages containing the subject of the message that would have been sent with the position, the ask isn't as large. Is something like
I had envisioned a link to the beginning of the thread, but the canned search example you propose is at least a 95% solution, and arguably better. If much easier, please do that.
Where to put the link? I would say the little "email requested to send with this discuss" envelope icon. But the text that says "Discuss (2022-06-30 for -09)" AND "Comment (2022-06-30 for -09)" , when there are both, would work too. I don't have a strong opinion.
It would be much easier - the datatracker currently has no way to calculate what the Archived-At header would be (and it may not be possible to make this calculation before bits have been added by the mail pipeline to begin with. We'd be left with adding scaffolding to give us a guaranteed unambiguous search.
Activity
rjsparks commentedon Aug 29, 2022
When I first read this, my reaction was that it's a pretty big ask. (Almost) anything is possible, of course, but this would require some interesting machinery, assuming what you mean is to link to the exact message using the Archived-At header for messages that have made it into the archive.
But thinking for a moment, if you mean, instead, a canned search that would match any messages containing the subject of the message that would have been sent with the position, the ask isn't as large. Is something like
what you're looking for? And if so, exactly where would you instinctively think to click to get there from the IESG evaluation tab?
martinduke commentedon Aug 29, 2022
I had envisioned a link to the beginning of the thread, but the canned search example you propose is at least a 95% solution, and arguably better. If much easier, please do that.
Where to put the link? I would say the little "email requested to send with this discuss" envelope icon. But the text that says "Discuss (2022-06-30 for -09)" AND "Comment (2022-06-30 for -09)" , when there are both, would work too. I don't have a strong opinion.
rjsparks commentedon Aug 29, 2022
It would be much easier - the datatracker currently has no way to calculate what the Archived-At header would be (and it may not be possible to make this calculation before bits have been added by the mail pipeline to begin with. We'd be left with adding scaffolding to give us a guaranteed unambiguous search.
martinduke commentedon Aug 29, 2022
SGTM
evyncke commentedon Nov 15, 2026
Hope that PR #12067 addresses your issue @martinduke