![]() ![]() You might also try to use the Redmine API to gather the necessary data. Depending on your setup, this might result in timeouts of your webserver. Note that there are limits of how many issues can be exported at once and that it might take a long time to create the files. Alternatively, you can also export the current fields of multiple issues as a CSV file (without the history). Issues can be exported as PDF files (including all history) by clicking on Also available as: PDF on an individual issue or issue lists.I managed a test with a ldap browser, but only after exchanging the certificate from the ldaps Server. I got a proxyuser for that and a certificate and should be able to connect over SSL and port 636. There, you can find an Also available as: HTML link at the bottom to export the entire wiki. I want our users to authenticate over the ldaps Servers. For wikis, you can find an export option on one of the index pages linked in the sidebar.Still, there are ways in Redmine to export data in human-readable form: ) it's not clear what exactly belongs to this project, partly also because a later import of the exported files are even harder. With that being said, there is no built-in way to export entire projects in Redmine, partly because with global data (such as users, trackers, issue statuses, shared versions, cross-project relations. Also, the data is not really browsable on its own. NOTE: If you use different names for your certificate and key files, you should reconfigure the SSLCertificateFile and SSLCertificateKeyFile directives in the corresponding Apache configuration file to reflect the correct file names. However, with that approach, you would ship all data contained in the Redmine to your customer, including unrelated projects and potentially private data. Copy your SSL certificate and certificate key file to the specified locations. ) and ship it to the customer as described by Jota Martos in his answer. You can export your whole Redmine installation (that is the database, uploaded files. ![]()
0 Comments
Leave a Reply. |