Enhancement Request:
We have been using QB built in Jira integration along with some custom groovy to carry out Jira rest calls as well as Jira client within QB to get all what we need and its working great !!!
 
However now that the teams are using Jira for a lot of their planning and management reporting, there is a request where teams want to be able to create jira release using QB, however not mark them as released.
 
Once the release candidate goes through SDLC pipeline, they want to mark it released only once it goes to PROD.
 
Based on this request, would it be possible to make the release|unreleased mark as a scriptable option. This will allow us to create the initial release candidate on QB build completion and mark it as unreleased and once the candidate / build is moved through the pipeline we can mark it as released.
 
I understand that you would have to default the value to released based on current existing behavior, which is completely fine.
When release a version, our Release Version Step will associate the issues specified with that version. If you don't want to release that version, do you still need associate those issues? or you just simply want to create an unreleased version in JIRA? If you just want to create an unreleased version, you can write some script to do that, let me know if you need this.

 
Question:
Same as accessing jira issue data using the tracker client (com.pmease.quickbuild.plugin.tracker.jira.client and its java rest api), is there any way to access version information for a given version using QB available java class and also is there any similar api doc for the same you can help provide.
 
Reason I ask this, is because, jira release module is very weak. It has no place for any additional user metadata. We wanted to add the environment information the given version is deployed to. For now we update the description example - PROD - Auto promoted by QB. However as soon as QB updates it, the existing description is over-written. One of the request is that if description exists, then prepend the environment and then past the existing description.
 
I can do all this but need a way to: 1) check if release exists 2) if so then check if description exists 3) if so then prepend the environment (with some checks) and then paste existing description.