Nic Brough -Adaptavist- Expert

You could put the "verify" status in the "done" column with your "closed" status.

So what are you doing differently to what the doc says and what are the symptoms?

Yes. The project table has "type", which is the Software/Business/Service Desk you've already found, but no template key.

Because your transition is set up to set the resolution to the value the person puts in the field. Retain values doesn't do anything because it's overwritten by the transition process.

No, restarting is not going to help. You have said the affected users are using a different network, and "could not be contacted" is consistent with networking problems, so you should be looking to fix your network slowness.

Ok, so you did not "do the same", you tried to delete your Atlassian account. According to the report, you have one or more active products that you are responsible for. You will need to shut them down (delete/unsubscribe), or make new owners for them. Once you have shut down or handed over all the systems, you will be…

Jira doesn't record the templates - they're only used while creating a project and aren't of any use after that because an admin can (and often does) reconfigure the project away from the template.

The parent key is not "just a field", it's a structural thing and can't be just set, you have to use something that can change the linked parent. I don't think you can do this in a simple Automation "edit fields"

You can set Jira to do this automatically - close sprint, all issues that are not "done" will move. How are you moving issues to the upcoming sprint?

My guess is that you are looking at a trial, a free, an academic, a charitable, or $10 starter licence. Developer licences only exist for Commercial licences at 25 users or above (I think. I'm not 100% sure about the academic or charitable ones)

You'll need to remove all the application access then.

A 200 is a success, now you're on the right url.

Could you give us the rest of the error? A code, completely out of context, is not of a lot of use.

Which "same" did you do? If you did mean your Atlassian account, then you missed something somewhere, as you are still able to post here.

I do not understand, I am sorry. It looks like you have a set of users, for whom Jira seems slow (especially in the mornings). The difference between them and people who do not experience slowness is that the users who see slowness are using a different network. Is that right?

A block of error with zero context or explanation is not the way to get any help.

Try selecting one single project that has the field.

These JQL functions do not support direct field comparisons. They can only compare date fields with absolute or relative dates. i.e. "<field date 1> is more than 5 days in the past" can be done, but "<field date 1> is after <field date 2>" can not.

But your curl call is over the default http port of 80. Have you set up 80 to serve up https? Or are you looking in the wrong place?

That's the display from "manage add-ons", try "manage applications"

In the section "connector port = 8090" why did you set the proxy port to the internal connector port instead of the port the proxy is going to be working on? The proxy connector settings that the error message is warning you about are for the external user-facing stuff, not the internals. Try changing it to 443 as suggested

You can disable it in "manage applications", but, although that does not lose any of your data, you will not be able to get to a lot of it, as the functions that read it have been disabled. The easiest route is probably to change who has access - change "can use Service Desk" to just "jira administrators" or an even…

Assuming you have completely deleted it, then you'll need to get a backup, restore that to a temporary Confluence installation, then you'll be able to export that single space from the temporary install and import it into the original Confluence.

The error you're getting is a network error - it means there is nothing running on port 80 (http) on the url you are hitting, or a firewall is stopping the connection dead. Check what the base url of the Confluence you are trying to connect to is, I suspect you will find it is not what you are using in curl (it will…

There is no supported way to fix these vulnerabilities other than to upgrade to a version that does not have them. If you were on a long-term-support (previously called "enterprise") version, then point-releases or patches from Atlassian would be available. But you are not, so your only options are to upgrade, or work out…

I the basic search, remove the selection for project. If you select a project in there, the basic search looks at whether each other field is available to that project, and tells you when it is not, so you don't end up with a query that won't work. JQL is actually less clever, it doesn't do any such checks, it just lets…

Neither, you don't apply a licence to Cloud. You buy a subscription.

Use a cascading select list instead of two separate fields. You could also do this with separate fields using the Behaviours module in the Scriptrunner app.

If you log in as the user the REST calls are authenticating as, do you get the assignee on screen when you start creating an issue?

* See https://www.atlassian.com/cloud-migration/explore-cloud * Yes * No, when you're on trial, you are not supported, but Atlassian will try to help. SLAs only apply if you have Cloud Premium as well. * Yes if you'd doing a migration, they'll help if something goes wrong * Yes