[ 
https://issues.apache.org/jira/browse/NIFIREG-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kevin Doran updated NIFIREG-141:
--------------------------------
    Description: 
On the backend, a bucket in NiFi Registry has an optional "description" field 
that can be used to convey the intended purpose of a bucket, or a more 
meaningful description than just what is used in the name.

This field should be settable (at bucket creation time and/or in the edit 
bucket side panel) and rendered in the table and/or detail view of a bucket in 
the NiFi Registry UI.

If NiFi is rendering this field, we should make sure that works correctly in 
collaboration with this ticket. If NiFi is not displaying bucket descriptions 
(for instance, when choosing where to initially save a flow), we should 
consider if adding that information is useful in the NiFi UI.

  was:
On the backend, a bucket in NiFi Registry has an optional "description" field 
that can be used to convey the intended purpose of a bucket, or a more 
meaningful description than just what is used in the name.

This field should be settable (at bucket creation time and/or in the edit 
bucket side panel) and rendered in the table and/or detail view of a bucket in 
the NiFi Registry UI.

If NiFi is rendering this field if set, we should make sure that works 
correctly in collaboration with this ticket. If NiFi is not displaying bucket 
descriptions (for instance, when choosing where to initially save a flow), we 
should consider if adding that information is useful in the NiFi UI.


> Bucket descriptions in the Registry UI
> --------------------------------------
>
>                 Key: NIFIREG-141
>                 URL: https://issues.apache.org/jira/browse/NIFIREG-141
>             Project: NiFi Registry
>          Issue Type: Improvement
>            Reporter: Kevin Doran
>            Priority: Minor
>
> On the backend, a bucket in NiFi Registry has an optional "description" field 
> that can be used to convey the intended purpose of a bucket, or a more 
> meaningful description than just what is used in the name.
> This field should be settable (at bucket creation time and/or in the edit 
> bucket side panel) and rendered in the table and/or detail view of a bucket 
> in the NiFi Registry UI.
> If NiFi is rendering this field, we should make sure that works correctly in 
> collaboration with this ticket. If NiFi is not displaying bucket descriptions 
> (for instance, when choosing where to initially save a flow), we should 
> consider if adding that information is useful in the NiFi UI.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to