I filed https://issues.apache.org/jira/browse/INFRA-16683 to get some info
/ feedback from INFRA. After a bit of searching, the ideal that Davor
described is definitely possible and even normal.
Kenn
On Wed, Apr 18, 2018 at 12:33 PM Kenneth Knowles wrote:
> Yea, the separation of commits@ and i
Yea, the separation of commits@ and issues@ was just a nice thing to make
both more readable. I could imagine looking at issues@ once in a while, but
never commits@. Not terribly important. But separating watching and
reporter is very helpful. Both devs and users may not want to actually
track some
commits@ or dev@ are common choices. Others are generally redundant or
means it is ignored by everybody which is fine but means you just drop
notif from jira instead of redirecting them ;)
Just my 2 cts
Le 18 avr. 2018 20:55, "Kenneth Knowles" a écrit :
> Annoyingly, it appears that the reporte
Annoyingly, it appears that the reporter is not automatically a watcher. It
is incorrect that it is a strict degradation, but I agree that it is not a
good change to make since it favors devs over users. I will chat with infra
about whether we can set up the best case.
In the meantime, perhaps I'l
An INFRA ticket is needed.
(As long as the report is automatically a watcher, the change is a strict
improvement. If not, it's a strict degradation.)
On Tue, Apr 17, 2018 at 1:55 PM, Kenneth Knowles wrote:
> Hi all,
>
> Currently, every touch on a JIRA causes four notifications:
>
> - all watc
Hi all,
Currently, every touch on a JIRA causes four notifications:
- all watchers
- current assignee
- reporter
- comm...@beam.apache.org
I think there are redundancies and imperfections here. If you report a bug
you cannot later unsubscribe from it! I may be disproportionately spammed
here
