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; } } }

So close! Add multiple accountID Strings to User Picker(Multi)

Evan Nixon

Hello!

I have had an unbelievable struggle getting this automation to do it's thing, and I'm very close to the finish line, hopefully someone can point out the silly mistake I've made and get this across the finish line.

Here's the layout as is.

Screenshot 2021-11-09 172425.png

The objective to give people the ability to flag a particular user in a comment by putting an exclamation mark after their mention. The automation should then pick up that user's ID string and add it to a custom multi-user picker.

Screenshot 2021-11-09 172657.png

Using a conditional check of {{comment.body}} for \[~accountid:.+\].*! works perfectly, and the below smart value (and string it outputs) seems like the right combination to put into the multi-user picker, but no matter what it gives me the below error in the log.

Screenshot 2021-11-09 173053.png

The second string in the log is a .asJsonArray render from the {{Test}} custom smart value, which has the same smart value is as in the JSON additional field - just with ".asJsonArray" at the end. I've attempted to have the two strings with no space between the comma and second string, only the comma, only a space, asJsonString, asJsonArray - no luck with any of them.

So after all this : what on earth is the delimiter or format needed for multiple id strings for them to to be accepted by a multi-user picker box?

Accepted answers

Darryl Lee

Hi @Evan Nixon -

Based on this documentation for overwriting a Multi-user picker custom field:

"customfield_11458" : [ { "id":"2s1863211f0z284c45269423" }, { "id":"332212e13z52142111269423" }]

Maybe for an ADD you would also use just id instead of accountId?

All comments

Darryl Lee

Hi @Evan Nixon -

Based on this documentation for overwriting a Multi-user picker custom field:

"customfield_11458" : [ { "id":"2s1863211f0z284c45269423" }, { "id":"332212e13z52142111269423" }]

Maybe for an ADD you would also use just id instead of accountId?

Darryl Lee

I guess you could call this the "documentation" for this:

Fields specified by an "ID" type use the attribute "id". For system user fields (only) we allow "accountid" as a synonym. For custom user fields you need to use "id", like:

{
    "fields": {
        "customfield_10055": [
            {
                "id": "0f0000fff0ffff0f0000f00f"
            }
        ]
    }
}

From JRACLOUD-72000

Darryl Lee

I have this excellent resource bookmarked, but completely forgot about it until researching the above answer:

JSON input for fields

Although @Radhika Vijji _Innovalog_ and @David Fischer suggest the correct format for User picker (Multi-users) is:

[{"accountId":"accountId:557058:3a41d4ee-3331-4363-8cdf-f90a2da92f7e"}], [{"accountId":"accountId:557058:3a41d4ee-3331-4363-8cdf-f90a2da92f7e"},{"accountId":"accountId:557124:3a41d4ee-3331-4363-8cdf-f90a2da92t4e"}]

So, now I'm not so sure about the "id" suggestion.

I suppose you could try them both.

Bill Sheboy

Hi @Evan Nixon

Yes, and...to what Darryl notes: If you expect there could be multiple mentions in the comment, I do not believe there is a built-in way to parse those values into JSON for the edit of a multi-value picker field.

A work-around is to get your id list into a created variable, and then use list iteration and text functions to dynamically build the JSON into another variable. Finally use that last variable in the update.

Kind regards,
Bill

Mike Espitia

Hello there,

I am trying to work something similar to extract from {{issue.comment.first.body}} The phrase that come after Sub Category. to enter into my custom field {{Issue.fields.customfield_10486.value}

Bill Sheboy

Hi @Mike Espitia

As this is an older thread, I recommend creating a new question, and perhaps linking back to this one for context. That will help ensure more people see the question to offer suggestions.

When you add the question, please include an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Thanks!

Kind regards,
Bill

Evan Nixon_qrlydp

What are the chances that I'd be working on re-implementing this feature on a completely new instance, find myself back on this thread (which has been dead for all 873 Days since I last went absolutely insane worked on this thing)...only to find another poor soul starting down the same doomed path I once walked? The universe is a weird place some times.

On an entirely unrelated note:
On behalf of all Jira Admins who have ever stood on the shoulders of the giant that is @Bill Sheboy : I'd like to express my absolute indignant disbelief at the "Rising Star" flair you're stuck with. Bill, you are a Rising Star in the same sense that a Shepard Tone is a rising note. Come on Atlassian. You've finally fixed The Curse of the Spooky View Profile Button , I think it's about time Bill's flair got updated to something more reflective of his years of service to this community. I don't know exactly what you should go with, maybe something short and snappy? Something like "Keeper of Wisdom and Knowledge Eternal"? No, that might get cut off in mobile. Maybe "jirAdmiral of the Forum-Fleet?". Or just keep it simple and classy: "Ya-Boi Bill Sheboy"?

P.S. @Mike Espitia I agree with Bill here: starting a new thread is definitely your best bet. This poor thread has suffered enough, as they always say in my Pedantryaholics Anonymous group: Let it RIP in Peace.

Welcome!

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

Quick Links

Find more posts tagged with

automation

json

regex