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

Why can't organization be set in automation rule?

Sabrina Liao

I want to be able to automate setting the organization for a ticket based on conditions of what's found in the description since we auto-resolve the tickets I'm wanting to create this automation rule for. However, the 'Edit Issue' action doesn't include 'Organizations' as a field as can set. Why is that?

Accepted answers

Veera_zqt9p1

Hi @Sabrina Liao ,

Edit issue action in the automation rules comes with only a few options and Organisation is not one of them.

We have been tracking this as a feature request: JSDCLOUD-4258 to include more options.

All comments

Veera_zqt9p1

Hi @Sabrina Liao ,

Edit issue action in the automation rules comes with only a few options and Organisation is not one of them.

We have been tracking this as a feature request: JSDCLOUD-4258 to include more options.

Mike Bowen

Hi @Sabrina Liao

Here is an alternative solution using the free plugin Automation LITE for Jira

I was able to successfully re-create your request based on a condition found in a description of a ticket/request.

For my test I used an incoming email to our Jira Service Desk.

WHEN: Issue Created (Rule is run when issue is created)
IF: Description contains test 123 (as an example)
THEN: Edit issue fields Organizations (specify the organization).

Rules

Automation Test 123 - 1.png Automation Test 123 - 2.png

Test:

Result:

Automation Test 123 - 3.png

-Mike

Sabrina Liao

I'm wondering what makes the other fields different that they wouldn't be included in the list.

Mark Wheeler_un9ybq

Not being able to set the Organizations field from another field in Jira Automation is really really frustrating. Atlassian must have deliberately restricted Edit Issue Fields to not allow other fields to be copied into the Organizations field. As a result I have a Jira Automation rule to prompt Reporters to set the Organizations field if it's blank, with an apology that this isn't automated.

I think if I understood the reason behind the restriction then I'd be able to live with it better. Alternatively we just need Atlassian to sort of Organizations once and for all.

Albert Kalytta

Exactly this @Sabrina Liao .

Further i feel like everytime i read about something being discused as a feature request it wont happen anyway. Even if the request is 4y old.

It is honestly very much annoying.

Also installing another costly addon every time for a single solution is not the way to go either.

I hope atlassian will start communicating more customer friendly in the future and further provide better documentation and reasoning regarding long time submitted community requests.

William Walker_0tv9vj

Hello all, I was able to set Organizations by using the following method.

In this example I am setting the Organizations field to "All Users."

Screenshot 2024-04-19 at 3.23.50 PM.png

To find out the value of a custom field I referred to this: https://your-domain.atlassian.net/rest/api/latest/field

To find the ID for the "All Users" value I referred to this: 'https://your-domain.atlassian.net/rest/servicedeskapi/organization'

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-desk

jira-service-desk-cloud