We need to be able to automate the Organization field, please add this ASAP

Upvote for being able to automate the Organization field. Need to be able to assign the only existing value to the field.

I would also like this functionality. Actually, I am surprised that it doesn't already exist.

I am seeking this behaviour as well. Required for using automation to create service desk tickets cross projects and having the original team able to see the created tickets.

Hola, me gustaría funcionará la opción de añadir Organización en los campos de los issue al crearse

1 vote for: be able to edit/set Organizations field by automation

One of our JSM projects are for an application we develop for another hardware developer client. Our client wants to be added to each Issue that their users report by an Organisation spicifically for the developer so any of a few supervisors included in this Org can follow and weigh in on the issues.

But trying to desgn a new Automation rule in Jira SM Cloud I find no apparent way to set a specified organization for every new created issue? Is it possible or is this also something that need development and fits under this improvement suggestion?

It would be helpful to be able to automate editing of the Organizations field name assigning another custom field's value to have to be more dynamic for the  multiple projects we have.

I would like to automate assigning organization based on whether the requester's membership to that organization... meaning if a requester of a JSM ticket belongs to an organization, I want to add his/her organization to the ticket.

When?

Weirdly I can create the desired Organisation automation at Installation level and then assign to only 1 Project, but it doesn't show up in the individual Project? 

I would like to automate selection of an Organisation when an issue is created.  This is not available through Project Automation but is available through Global level?  Confused... 

I would like Automation to perform the following:

(1) Set the organization based on the user's email address
(2) Set the organization based on the value of a label

Hi,

I see the corresponding JSDSERVER-4258 is closed as resolved. Will the fix be implemented in the cloud version too?

Add Resolution to the Edit option.

We use the Resolve status to mark tickets as Resolved.

However, due to sheer volume of tickets, we need automation to monitor issues that are in "Waiting for customers" and have no activity for X duration of time.

When that condition is met, I need AUTOMATION to set the ticket to Resolve with a specific resolution status "No Response", for example.

So having the ability to get automation to set the resolution is making our lives easier. Also, this is just one use case... there are many.

Please promote this in your queue and add the Resolution in the Edit Issue for automation.

I'd like to edit the organizations field with an automation rule in cases where agents create issues but forget to assign it.

In Cloud more options are added, not sure if/when these are added in the server version.

I'd go further and suggest the inclusion of resolution, which isn't directly editable. At the moment, if you fire the automation "Transition", and you select a transition to mark the issue as resolved, the resolution is left unset and there isn't a solution to this problem.

Adding resolution to the list of fields you could change through automation would resolve this challenge.

It's kind of crazy that this is not possible. If you have a custom field available on an SD issue. I don't see why in the world you would not be able to set it during an automation rule. Is this just a cloud restriction or is this also the same on server?

The Suggested Resolution would be ideal. Thank you.