I've been playing with JIRA's built-in email digest subscription to see
what it's like. At the bottom of this email is the first part of it,
edited to be a fewer number of issues. See
https://confluence.atlassian.com/jiracoreserver073/working-with-search-results-861257284.html?_ga=2.58203242.1970990754.1565278227-958989.1565278227#ReceivingSearchResultsviaEmail-SubscribingtoaFilter
for further details.
My vote:
[v ] One daily digest mail per day with a list of new JIRAs
Rationale: I think this should cater to new/interested users, not us
committers that are always tracking the latest activity. We don't need any
change; we have all the mail to filter as we want. A new user may not want
to subscribe to the firehose of issues@ which may be overwhelming. The
only thing I can think of that counters this notion is that users could
just as well use JIRA to set up their own subscription to their tastes,
perhaps to a different schedule or only looking at Lucene or whatever. But
it's a little complex to do and they might not bother.
~ David
----------- SAMPLE EMAIL ---------
Issue Subscription
Filter: Solr Recent Updated (23 issues)
Subscriber: dsmiley
Key Summary
SOLR-13101 Shared storage support in SolrCloud
https://issues.apache.org/jira/browse/SOLR-13101
SOLR-7353 Duplicated child/grand-child docs in a block-join structure
should be removed by the shard hosting the docs not by the query controller
https://issues.apache.org/jira/browse/SOLR-7353
SOLR-6596 Atomic update and adding child doc not working together
https://issues.apache.org/jira/browse/SOLR-6596
SOLR-12638 Support atomic updates of nested/child documents for
nested-enabled schema
https://issues.apache.org/jira/browse/SOLR-12638
SOLR-13778 Windows JDK SSL Test Failure trend: SSLException: Software
caused connection abort: recv failed
You may edit this subscription at:
https://issues.apache.org/jira
/secure/EditSubscription!default.jspa?subId=22320&filterId=12347195
