The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Modifying issue in background job

Tomasz Belina
June 13, 2013
I have to change fixversion field in background job. Unfortunately solution described here https://developer.atlassian.com/display/JIRADEV/Performing+Issue+Operations doesn't work. There is no validation problems, no errors, nothing. Fix version remains unchanged. Is There something special which needs to be done to make it work in jobs ? Jobs is created using SAL (according to this article - https://developer.atlassian.com/display/DOCS/Scheduling+Events+via+SAL+Tutorial)

2 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Tomasz Belina
June 20, 2013
Code looks like this:
IssueInputParameters pNewIssueInputParameters = issueService.newIssueInputParameters();

pNewIssueInputParameters.setFixVersionIds(pNewIds);
UpdateValidationResult pValidationResult = issueService.validateUpdate(aUser, aIssue.getId(), pNewIssueInputParameters); if(pValidationResult.isValid()){ if(logger.isInfoEnabled()){ logValidationResults(pValidationResult); } IssueResult pUpdateResult = issueService.update(aUser, pValidationResult,EventDispatchOption.ISSUE_UPDATED,false); if(!pUpdateResult.isValid()){ logger.error("Can't update issue: "+aIssue.getKey()+". Reasons:"+ pUpdateResult.getErrorCollection()); } }else{ logger.error("Can't update issue: "+aIssue.getKey()+". Reasons:"+ pValidationResult.getErrorCollection()); }

My first thought was that there is something wrong with security context. So before calling issue service I added something like this

JiraAuthenticationContext pJiraAuthenticationContext = ComponentAccessor.getJiraAuthenticationContext();

		pJiraAuthenticationContext.setLoggedInUser(pUser);

Things became better now and on developer jira instace its started to work. Unfortunatelly on testing env it doesn't.

Interesting thing is that on dev env - before adding:

pJiraAuthenticationContext.setLoggedInUser(pUser);

there was no entry in Map returned pValidationResult.getFieldValuesHolder() about new fixversions.

0 votes
Jobin Kuruvilla [Adaptavist]
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 Champions.
June 13, 2013

Maybe you can post your code here?

TAGS
AUG Leaders

Atlassian Community Events