Part of story #12345 export results to csv In contradiction to the acceptance criteria of this story, we must provide a second route. Since the returned Artifact representations are fixed in the regular cross-tracker REST route and since they do not use duck-typing at all, it is necessary to offer another endpoint. We made the choice not to use Restler because that would mean enabling CSV representations for ALL REST routes, which is not desirable (and apparently also broken). Thus, this introduces a FrontRouter-enabled endpoint to retrieve paginated CSV. The route is still paginated to avoid performance problems and DOS. How to test: - Browse to /plugins/crosstracker/csv_export/<report_id>?limit=50&offset=0 - The browser should offer to download a CSV file with "id" as header and the list of artifact id of the given Cross-tracker report. - When you omit limit / offset, you should get a 400 error. - When you set limit > 50, you should get a 400 error (Same limit as the REST route). - When you don't have permission to view the project of the associated widget or when you don't have permission to view a project used in the query, then you should get a 403 error. - When the project can't be found, you should get a 404 error. Will be done later: - CSV Export button that takes pagination into account - CSV Export of other "Always-there" fields Change-Id: I9d33010cb1f5683dff2d649bc45f21af67cd3f08

+741 −5

Author

Joris MASSON (jmasson) 2018-10-17 12:15

Committer

Joris MASSON (jmasson) 2018-10-22 11:25

Hash a2ee1b483df526469a4234527367430ab3bc7102

Parent ec46ebd6583355cf16c115637ba65987de30dd20

Reference git #tuleap/stable/a2ee1b483df526469a4234527367430ab3bc7102