Need help with the subject, code runs inside Create Issue SR listener. Spent substantial time trying to break through various ways to update an issue within a context of scriptrunner listener, to no avail. Looks like the best practice has evelved multiple time over last few years. The code doesn't complain during runtime, yet fails to update security level. Thanks for your suggestions.
... [set value to secLvlId]
def iSvc = ComponentAccessor.issueService
def user = ComponentAccessor.jiraAuthenticationContext.loggedInUser
def params = iSvc.newIssueInputParameters()
params.setSecurityLevelId(seclvlId)
def validationRes = iSvc.validateUpdate(user, issue.id, params)
if (validationRes.isValid()) {
iSvc.update(user, validationRes)
} else {
log.warn """Unable to perform the issue security level update to $seclvlId!
Issue:$issue
Error:$validationRes.errorCollection"""
}
Is "seclvlId" the security level id as a long? Where are you getting the id from? Does the user who created the triggered the listener have permissions to update the security level?
If some of these things had happened I would have expected to have seen a message in the logs. Is there nothing in the logs?
It is not a long, no, just a regular constant assigned to it, like 10101. I am an admin, so I believe both questions on a user are yes. Nothing in the logs, except my messages from log.warn.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That should be ok, as long as that security level id exists in JIRA. Groovy will convert it to a long.
You mention you see you log.warn in the logs. Do you see the error? You previously mentioned you didn't but just wanted to check.
Could you please post your full script? Then I'll try it out.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.