Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

Why can't organization be set in automation rule?

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?

3 answers

1 accepted

0 votes
Answer accepted
Veera Atlassian Team Jan 15, 2020

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.

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

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.

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.pngAutomation Test 123 - 2.png

Test:

Automation Test 123 - 4.png

Result:

Automation Test 123 - 3.png

-Mike

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.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

Announcing Jira Service Management!

Hello there Cloud Community members! Today, we’re thrilled to announce Jira Service Management, the next generation of Jira Service Desk. Jira Service Management touts advancements in IT service ...

2,198 views 28 39
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