[ 
https://issues.apache.org/jira/browse/NIFIREG-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16316807#comment-16316807
 ] 

Joseph Percivall commented on NIFIREG-77:
-----------------------------------------

[~bbende] when I originally created the ticket I was thinking of the view 
within NiFi but given this is the Registry Jira, I agree with you that it 
should focus on the Registry side and we'd create a ticket for the NiFi side.

Partially I didn't want to create a bunch of tickets in the NiFi Jira at the 
time because the core PR wasn't merged yet. Now that's merged we can go that 
route though.

> Allow a user to see the changes created by the currently loaded version
> -----------------------------------------------------------------------
>
>                 Key: NIFIREG-77
>                 URL: https://issues.apache.org/jira/browse/NIFIREG-77
>             Project: NiFi Registry
>          Issue Type: Improvement
>    Affects Versions: 0.1.0
>            Reporter: Joseph Percivall
>            Priority: Critical
>
> As a user, I would like to see the changes that are included in a particular 
> version. More specifically, if I'm on an old version and I upgrade to a 
> version written by someone else, I have no way to know what changes occurred 
> during that version upgrade.
> A simple solution would be to utilize the same logic which displays the 
> current differences between local and stored in the registry and use that to 
> show the differences between the current version N and version N-1. The user 
> could then change between versions to see the changes that happened as part 
> of that version.
> An even better solution (from a DFM perspective) would be to be able to see 
> the changes within any version (not just the most recent). That way a DFM 
> wouldn't have to stop the flow for an extended period of time to view the 
> changes/differences in different versions but I think that'd be more work.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to