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

Edit Issue Custom Single-User Field

tmaliszewski

Hi All,

I am trying to define Automation rule for my team to automatically assign fields. I am struggling with a custom field type single-user picker. My field is not available via the 'Choose fields to set..' so need to go with JSON.

I tried following but none of the works:

{"fields": {"customfield_10829" : { "name": "61ead3cc9d1740006900db46"}}}

{"fields": {"customfield_10829" : { "id": "61ead3cc9d1740006900db46"}}}

{"fields": {"customfield_10829" : { "name": "currentUser()"}}}

{"fields": {"customfield_10829" : { "id": "currentUser()"}}}

also tried all above with using update/set but still getting same result, an error

(data was not an array (customfield_10829))

Ideally I would like it to work on a team level so it should assign the field for current user.

Not sure where I am making things wrong.. Appreciate your help!

Accepted answers

All comments

Ste Wright

Hi @tmaliszewski

What's the full rule? I assume the user picker is a custom field, not the assignee field?

It'd be good to clarify some things about the field also...

Is the field on the Screen?
Is it a visible field - i.e not hidden in the Field Configuration?

^ Because if it's a normal User Picker (Single User), it should be possible to use without JSON.

For example, I used a custom field, Owner, and then used this rule to populate it:

Trigger: Issue Created
Action: Edit Issue
- Field: Owner
- Value: {{initiator}} - this Smart Value populates Owner with the user who triggered the rule

Ste

tmaliszewski

Hi Stephen,

Thanks for your response.

The full rule is:

Trigger: When issue created

Condition: Reporter is current user

Action: Edit Issue (advanced = JSON, as the custom field I want to edit is not showing up on the drop down list. On the drop down list is a text: AVAILABLE FIELDS SHOWING 50 OF 391, but the custom one I am looking for is not there)

My JSON in the advanced edit issue is following:

{"fields": {"customfield_10829" : { "name": "61ead3cc9d1740006900db46"}}}

I tried all the above options but with same error.

Ste Wright

Hi @tmaliszewski

Is the field available if you search for it in the Choose fields to set field?

As I say, it'd be good to clarify why the field isn't showing rather than trying to resolve it with JSON (which still might not work if there's a reason the field is not editable).

It should be there in the list, there's no reason above which states otherwise.

Ste

tmaliszewski

Thanks Stephen,

Let me dig into it to try find out why that field is not showing up on the Choose fields field.

Thanks!

Tomasz

Mark Chaimungkalanont

Is the field in question a People field in one of the Team managed project types? That field type isn't supported yet, which may explain why it doesn't appear on the list

tmaliszewski

Hey Mark,

My field is a custom field defined on a project level and it is user field. Are you saying that type of field is not supported in the automation rules yet?

Welcome!

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

Quick Links

Find more posts tagged with

cloud

automation