Nic Brough -Adaptavist- Expert

That would suggest the base url is set to the ip address, or the proxy settings are doing something odd.

See https://www.atlassian.com/trust/reliability/infrastructure - it's based on where the majority of your users are active. (Remember that you can ignore the outdated stuff on Privacy Shield on that page, as it's now irrelevant). You can request to keep your location inside the EU I believe, as a support request/

Go to the project that you want to do this in, then go to its admin area and look for the "issue type scheme". You'll need to descend into that and edit it, so that for your issue type(s), they use different screens for create, edit and view - the minimal difference being the create and edit screens do not include the…

Not with Automation, although there are some other apps that can set it.

The fields you have in red are not to be set by the customer, so there's no point putting them on the request screen.

So you'll need to look at why Cloud cannot reach it from the outside.

This is quite complex to explain, but I'll try to keep it simple. When you "install an app" in Jira Cloud, most of the time, you are not really installing anything. You are telling Jira "there is a remote application I want you to talk to". This remote thing is expected to give Jira a response that confirms that it will…

I don't think you can customise the recipients by request type. See https://confluence.atlassian.com/servicedeskserver/managing-service-desk-notifications-939926348.html for what you can do

Ok, well, it is an old article, and I suspect it was written for Server, where you're on Cloud. The Automation function you are trying to use there does not support original estimate as a field it can set.

This is where we look to the "issue type screen scheme". These schemes tell a project what screens to use for some actions. For example: * For bugs* Create screen = bug create screen * Edit screen = bug edit screen * View screen = generic view screen * For features* Create screen = bug create screen * Edit screen = feature…

Install or uninstall? (I am sorry, I can't guess which from "unstall")

Why are you fixated on JSON code? The version of Automation you have here is clearly different to the one in the post from 2 years ago. In the box on the far right, select the field you want to update and give it the data it asks for when you've selected.

I've just changed permissions on a whole Jira system excluding attachments in less than 10 seconds. The attachments (around 60 thousand) took less than a minute. I have some concerns about your file systems if it's taking 30 minutes to do a simple chown.

Yep, that's the one - "any logged in user" has "browse project". You'll need to reivse that, exactly as @Patricia Francezi_iDev_ says

You say the fields you are reading are select-lists. The fields will contain "options" which you can't just cast to an integer because they are a complex object. Imagine a list of animal species - you can't just say "what number is an elephant?" You could try to get the name of the option as a string, and use parseInt oon…

I'm sorry, I thought the question was about the mention of the email. To grant them access, you will need to log in as someone who can manage restrictions in the space, go up to the top-level page that is blocking access, and edit the restrictions on that, adding this new person in to the list of people who can see the…

You have not selected a field to edit, so it can't know what to ask you for.

Ok, so you can ignore the bit about email then.

Just to add to this, you say "In the permission schemes i have checked and they are not allowed access" - this statement is clearly incorrect. If you have people who can see a project, they are allowed access by the project's permission scheme. Have another look and look at the users, groups, project roles and dynamic…

I am sorry, but that sentence is not clear. Nor does it contain a question or any explanation of what you are looking for us to talk about.

You can't have a status with two different names - a status is a name for a position in a workflow step. If you want to have different step names in a workflow, then, yes, you will need to add new status for each new name you want.

When someone asks for access to a page, it emails the people who have the right to grant it.

You'll need to map the stored options in the drop-downs on to numerics.

There is nothing to do on "inbound". Jira has a REST API you can use already, it's built in and always available. For "outbound", you'll need to find or write something that makes REST calls out to Servicenow. I would start with a look in the marketplace.

It is not a memory leak - the symptoms of those is that the memory usage increases and never drops, eventually reaching the max and falling over. It is perfectly normal to see memory usage going up and down in a Java application. The error messages you are posting are in fact only warnings that the JVM is about to clear up…

I am not sure what you are asking when you talk about "activate". Automation has fields which expect JSON input in some places. If you're using an automation rule that needs it, it will ask you. The post you've mentioned is about setting up a rule to change the estimate and that particular rule expects json.

Your app will need to replicate all the functions of the Jira issue collector itself, including login and asking for fields, but because it is outside Jira, it will also need to poke the data in via REST

Advanced Roadmaps, Jira Align, and Structure all have options for layers over Epics

The config you have given me here seems to say everything should be working, so I am a bit stuck. My best guess is that the next place to look is at the detail of the proxy, as that is not referring back to Confluence like it is to Jira. I would want to check that both services are available on the addresses the proxies…

You do not. The hierarchy in Jira Software is Epic -> Story -> Sub-task. You can't add more layers without apps that add them.