[
https://issues.apache.org/jira/browse/NIFIREG-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFIREG-65:
-------------------------------
Description:
Currently, {{GET /buckets/:id/flows/:id/versions}} returns a list of all flow
versions in ascending (i.e., oldest to newest) order.
The user / UI is interested in the most recent versions first, so we should
change the ordering to be by descending version number (i.e., newest to
oldest). While this could be done client-side, if pagination gets introduced
that would complicate things. So it will be better to return this order from
the rest api to make it easier to display.
was:
Currently, GET /buckets/{id}/flows/{id}/versions returns a list of all flow
versions in ascending (i.e., oldest to newest) order.
The user / UI is interested in the most recent versions first, so we should
change the ordering to be by descending version number (i.e., newest to
oldest). While this could be done client-side, if pagination gets introduced
that would complicate things. So it will be better to return this order from
the rest api to make it easier to display.
> List of flow versions should be returned in order of newest to oldest
> ----------------------------------------------------------------------
>
> Key: NIFIREG-65
> URL: https://issues.apache.org/jira/browse/NIFIREG-65
> Project: NiFi Registry
> Issue Type: Improvement
> Reporter: Kevin Doran
> Priority: Minor
>
> Currently, {{GET /buckets/:id/flows/:id/versions}} returns a list of all flow
> versions in ascending (i.e., oldest to newest) order.
> The user / UI is interested in the most recent versions first, so we should
> change the ordering to be by descending version number (i.e., newest to
> oldest). While this could be done client-side, if pagination gets introduced
> that would complicate things. So it will be better to return this order from
> the rest api to make it easier to display.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
