Modifying issue in background job

Question

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)

Tomasz Belina · Answer

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.

Jobin Kuruvilla [Adaptavist] · Answer

Maybe you can post your code here?