Storing the information is still possible (with the --save-passwords option). If the information is already present in the config file (as would be the case for people upgrading) then nothing changes.
The commit message of the last commit explains in detail what different usage scenarios are and how this change affects users.
SSL certificate path
Allow specifying the path to your SSL/TLS CA certificate bundle in the _verifyssl config option.
I tested this successfully with JIRA but I currently don't have a Redmine instance so I couldn't test it there. All the changes are tested with JIRA.
This pull request also includes the previous changes because GitHub does not seem to support pull requests that are based on each other...
Custom JIRA transition name
Allow specifying custom JIRA transition names (e.g. "In Progress" instead of "Start Progress" in my case)
Sensitive data
Storing the information is still possible (with the --save-passwords option). If the information is already present in the config file (as would be the case for people upgrading) then nothing changes.
The commit message of the last commit explains in detail what different usage scenarios are and how this change affects users.
SSL certificate path
Allow specifying the path to your SSL/TLS CA certificate bundle in the _verifyssl config option.
I tested this successfully with JIRA but I currently don't have a Redmine instance so I couldn't test it there. All the changes are tested with JIRA.
This pull request also includes the previous changes because GitHub does not seem to support pull requests that are based on each other...
Custom JIRA transition name
Allow specifying custom JIRA transition names (e.g. "In Progress" instead of "Start Progress" in my case)