Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Using "issue.assigneeId =" in Workflow post function script not working for edited JIRA accounts

Environment - Adaptavist ScriptRunner v5.3.5 with JIRA v 7.4.4

Using the "Clones an issue" Script Post Function, one of the actions is to assign the issues to specific JIRA accounts using:

issue.assignedId ="xxx"  

It works for 50 out of 52 different Cloned issues, and the 2 that do not work are accounts where the Username of the JIRA account had been edited.  The specific entries are as follows:

issue.assigneeId = "cable_jiras"
issue.assigneeId = 'mcp_jiras'

All Clones are properly created, but for these 2 Cloned issues instead of the associated Full Name for the account appearing as the Assignee, it is the value entered within the " "".  (1st screenshot). No notifications are sent to the account, and using filters it does not show as being assigned to that account. 

Attempts to assign from the View screen shows the erroneous entry along with the actual entry. (2nd screenshot) 

Both of these account as used as Component Leads for several of the Components, and this works properly, it is only the assigment through the Post Function script.

Toggling the JIRA accounts to Inactive and back to Active does not change the operation. Neither did re-indexing or restarting the server.

I verified it is the editing of the Username by testing with other accounts.   

Both of the above accounts are associated with a number of issues and are tied to automation from other systems, so creating new accounts is not something the teams are interested in doing.

Thanks,

image.pngimage.png

 

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase

The benefits of using Jira in different departments

Jira is a great tool to use across different departments. Forget that paperwork – switch to Jira and get that tasks done smoothly. Marketing Jira allows for a complete digital transformation of you...

75 views 0 4
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you