Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Jelly Create Issue with versions and fixVersions

Ronald Horner
Contributor
June 9, 2011

I am working through transitioning from an inhouse tool into JIRA 4.3. The Jelly Tags [1] for CreateIssue show versions and fixVersions should be assignable. The code I'm using looks something like this (edited for proprietary information)

<JiraJelly xmlns:jira="jelly:com.atlassian.jira.jelly.JiraTagLib">
     <jira:CreateIssue
         project-key="PROJ"
         issueType="New Feature"
         summary="Provide images"
         priority="Major"
         versions="PROJ.4"
         fixVersions="PROJ.5"
         assignee="transfer"
         reporter="user"
         description="Project: GT Provide requested images on the server. "
         created="2002-07-15 00:00:00"
         issueIdVar="S2077id"
         issueKeyVar="S2077key"
         duplicateSummary="ignore">
      </jira:CreateIssue>
</JiraJelly>


The issue is created correctly, however the versions are not assigned to the issue. I tested this again with the test Jelly scripts from the source distribution, create-issue.test.create-issue-with-multi-versions-components.jelly, and it also failed to assign the versions to the issue.

Jelly throws no errors during execution, and when tested using non existing versions it threw the appropriate error, so it is safe to say the attribute is being parsed and processed. Is there a permission or setting that I am missing in my JIRA configuration?

[1] http://confluence.atlassian.com/display/JIRA043/Jelly+Tags#JellyTags-jira%3ACreateIssue

2 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Answer accepted
Jason Jason
Contributor
June 15, 2011

Here are some things to try

1. Make sure the versions are defined in the Jira Project (The versions have to exist before you can use them)
2. Make sure the two version fields show up on the create issue screen in jira. This can be a problem when creating issues via SOAP API, so Jelly might have the same limitations.

0 votes
Ronald Horner
Contributor
June 15, 2011

Thank you Jason. I had forgotten that I removed those fields from my create issues screen. Once I added them back in everything worked as expected!

Andrei [errno]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 16, 2011
just an fyi... you should use "comments" to comment on questions/answers
TAGS
AUG Leaders

Atlassian Community Events