Open
Bug 1472214
Opened 7 years ago
Updated 7 years ago
Link to herald transcript in emails triggered by herald
Categories
(Conduit :: Phabricator, enhancement, P5)
Conduit
Phabricator
Tracking
(Not tracked)
NEW
People
(Reporter: tjr, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: conduit-triaged, conduit-upstream)
I set up a couple of Heralds in Phabricator, which I think is a fantastic feature that I want to introduce everyone to. But very quickly I found that they were unusable for a number of reasons.
One is that the email has no indication hat it is a Herald email. Another is that it doesn't explain _what_ Herald is triggering. If I have multiple heralds set up, I might get a trigger for any one of them but not know which one I should be investigating.
Comment 1•7 years ago
|
||
If this is for debugging why you are getting notification, https://phabricator.services.mozilla.com/herald/test/ or https://phabricator.services.mozilla.com/herald/transcript/ (click Edit Query and add the phab commit identifier) will show you what herald rules are run for a particular commit.
That doesn't help if you have multiple herald rules that you want to look at different things in response to, that aren't immediately obvious from looking at the commit in question.
Investigating further, it looks like herald also allow you to set flags in response, which are private, so you could have each rule set a different flag, which you could then see when you look at the commit. I'm not sure if that would show up in the commit email. This definitely feels like a bit of a workaround, but is perhaps a reasonable stop gap until something better is implemented.
Comment 2•7 years ago
|
||
There will be a message in the Phabricator "Mail" application[1] for every email it sends you. If you visit the "Delivery" tab for a message, it should indicate if any herald rules caused it to be sent. If you see it was caused by herald you can go to the herald transcripts[2] and search for the related "Object Monogram" (This would be D<#> for a revision, something like rLANDOAPId8bbe4ec8d9c for a commit). There will be an entry for each time the object had an event that could send email, viewing the transcript will show you all the herald details.
All that being said, probably would be nice if the email itself had a link to the transcript if it was triggered by herald.
[1] https://phabricator.services.mozilla.com/mail/
[2] https://phabricator.services.mozilla.com/herald/transcript/query/advanced/
Keywords: conduit-triaged
Summary: Herald emails do not explain that they were caused by a Herald or why/which Herald → Link to herald transcript in emails triggered by herald
Whiteboard: [phabricator-backlog][phabricator-upstream]
Comment 3•7 years ago
|
||
Little update that might help, Phabricator sends a 'X-Herald-Rules' header on the mails it sends, (e.g. "X-Herald-Rules: <28>, <29>, <34>, none, <31>"). You can also turn on "Stamps" which will add things like "actor(@imadueme) application(Differential) author(@imadueme) blocking-reviewer(@mars) herald(H28) herald(H29) herald(H31) herald(H34) monogram(D2097) object-type(DREV) phid(PHID-DREV-67zbvvo3eqybl7yscpxl) reviewer(@mars) reviewer(@smacleod) revision-repository(rLANDOUI) revision-status(needs-review) subscriber(@mars) via(web)" to the body of the emails phabricator sends (duplicating a bunch of the custom phabricator headers, useful for gmail filtering).
You could use this to find out what is triggering. Still might be value in at least linkifying things though.
Keywords: conduit-backlog,
conduit-upstream
Whiteboard: [phabricator-backlog][phabricator-upstream]
Keywords: conduit-backlog
Priority: -- → P5
You need to log in
before you can comment on or make changes to this bug.
Description
•