Hi All
I'm starting to hit the 5000 automation limit.
The main culprit is an automation I setup to solve an issue in Jira. When a ticket is created, if the "Organization" field is blank, an automation reads which org the user is in and populates the field.
I'd rather not pay Atlassian any more money. How do I get the Organization field to work as expected without running an automation?
Regards
Shaun
Hi @Shaun Neighbour ,
I hope you're doing well.
If you are hitting Atlassian automation limits, then maybe it's to move out of A4J and use an automation tool.
I've suggest you to take a look at Power Scripts for Jira Cloud
We have some routines that'll help.
https://appfire.atlassian.net/wiki/spaces/PSJC/pages/756089148/Organization+Functions
Give it a test and if you have any questions or use case that you'd like to achieve, the Appfire Support team will be happy to review it and see on how it can be achieved.
I hope it helps.
Thank you,
Hector
Hi @Shaun Neighbour ,
I'd suggest looking in to this article https://confluence.atlassian.com/jirakb/requests-automatically-shared-with-organization-1107626894.html
If this setting is enabled the requests should be auto shared with the organization the customer is in.
Sidenote: the customer can choose to not share it with the organization and if the customer is in multiple organizations the default is to be shared with "none" but the customer can select the correct one at creation
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I just need the reporter's organization to appear on the ticket so the appropriate agent can be alerted.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Shaun, I could be wrong, but I believe this is the only way to do it with the base application. I'm in the same boat that I'm using an Automation to fill in this field.
I too would like the user's organization to default into the JSM ticket. Have you ever created a ticket with Atlassian Support? I would think this should become standard behavior for this application. Knowing that you're getting close to your Automation Limit may have some more weight to get this added as standard functionality.
I didn't have luck when I tried, but maybe if you give it a shot we might make some headway.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.