nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

AssigneeId not recognizing 20character length username

Kevin Lynch4

I've created a Script Runner Clone post function in my workflow. In the 'Additional issue actions' I have 'issue.assigneeId = "csramdocscoordinator"'

but when the ticket is created, it does not link to the user with this Id. instead it shows 'csramdocscoordinator#1' in the Assignee field.

How do I get it to recognize the Id correctly?

Accepted answers

crf

The "#1" comes from the automated rename of the userkey <=> username mapping that we hold onto for deleted accounts. If you rename a user such that you reclaim a username that previously belonged to somebody else, the mapping for the old owner gets #1, #2, etc. added to it until we find one that gets it out of the way. This is because we still keep the mapping for deleted users in case something is still referencing them and tries to look them up later.

The assigneeId is probably supposed to be the user's key, not the user's name, so you are setting it to the wrong account. You can use UserKeyService.getKeyForUsername to find the correct value.

All comments

crf

The assigneeId is probably supposed to be the user's key, not the user's name, so you are setting it to the wrong account. You can use UserKeyService.getKeyForUsername to find the correct value.

crf

As an example:

Create user "alice" (her key is "alice")
Create user "bob" (his key is "bob")
Delete "alice"
Rename "bob" to "alice". Behind the scenes, this forces the old "alice" to be renamed to "alice#1", so we now have:
key "alice" <=> username "alice#1"
key "bob" <=> username "alice"
Use "alice" in something that works with user keys

Now:

When you use "alice" is a username, you get the current "alice" who used to be "bob".
When you use "alice" as a user key, you get the old "alice" who got renamed to "alice#1".

To work with renamed users correctly, your code needs to use keys and usernames correctly. You've used the wrong one, here.

Kevin Lynch4

According to select * from cwd_user where user_name like '%sramdocscoordinator%' the only entry is the ID=53942 / USER_NAME=csramdocscoordinator

crf

A deleted user would not be in cwd_user anymore. You would find the record in app_user.

Kristian Walker _Adaptavist_

Hi Kevin,

Using the issue.assigneeId method expects the ID of the user as a paramater and not the username of the user as described here.

What you should look to do is to get a new user object for the user and set this using the issue.assignee method as shown below.

import com.atlassian.jira.component.ComponentAccessor

// Get the User we want to set as the Assignee on the cloned issue
def user = ComponentAccessor.getCrowdService().getUser(("kwalker"))

// Set the Assignee based on the username and not by key.
issue.assignee = user

image2016-3-11 11:27:16.png

I hope this helps

Thanks

Kristian

image2016-3-11 11:27:16.png

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

scriptrunner

jira

jira-administration

jira-core

post-function

clone