Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/2431
Should we add the ID as well? The name may not be unique, which although
that can be used strategically to "group" things with RouteOnAttribute, it's
not exactly "distinct". The onus could be on the user to uniquely name their
reporting tasks, but if they had access to both attributes, they could do
different levels of grouping, filtering, etc.---
