Added support for project version and added label "SDElements"
Expand the SD Elements label with a hyphen
"Project version" added to REST API, and a 'SD-Elements' label
Merge branch 'master' into jira_project_version
fixed the project version assignment and added remotelink to new issues
Merge branch 'fix_jira_priority' into jira_project_version
Solved both the SSL and Proxy issues with SOAP. Later we can extend this to the whole library
Normalizing all the HTTP(S) usage to go through SSL Cert validation and capability to specify proxy
small bug fix
Fix priority map and missing code
Project versions are handled better

Use a version name, instead of an internal id. We will only create a
single SD Elements issue in JIRA, no matter how many affected versions.
Update issues with new version if applicable

removed rogue print statement
Apply a project version if applicable

Remove some duplicated code
Fix spelling mistake
Tidied-up the exception handling
Project versions supported in JIRA 4 and 5

An optional project version in the sync settings enables users to re-use
a JIRA issue across a single project. When a new project version is
detected, the issue is automatically re-opened.

JIRA 4 checks that the project version already exists. JIRA 5 does not,
yet.
Check that a project version exists before applying it to a JIRA 5 issue
Merge remote-tracking branch 'origin/master' into jira_project_version
Move the parse_response() to the child class

Empty REST replies "" are acceptable only to JIRA 5 - we still require
JSON for every other SDE Tools REST client.
Merge branch 'master' of github.com:sdelements/sdetools into fix_jira_4