Nic Brough -Adaptavist- Expert

My guess would be that your "ETL" is not stable - either it, or your network, are not completing all of the calls being made. 60,000 calls for one issue is a massive load and I would have to say you're simply going to get errors when you overload a system like that. There's no question that that many calls to get data is a…

This usually means the operating system is not allowng access to the files mentioned in the directory named in the error message. Check the permissions, ownership and existence of the directory and files within it.

I do not understand the question. What do you mean by "boolean text string terms"? Could you write out the condition you are trying to construct in plain English? Give us an example rather than try to talk about logical structures?

You need to do what the error message says. Remove one or more existing gadgets to make space for the new one. The number of gadgets on a dashboard is capped, in order to prevent people building dashboards that do too much for the server and client to handle in a reasonable time.

Not from Jira, see https://developer.atlassian.com/server/jira/platform/database-schema/ Be aware that reading a Jira database is the single worst possible way to get at Jira data. The database is not a real database, it is a data store, and is the precise opposite of anything you would want to design reporting on. You…

I am sorry to deliver the bad news, but Atlassian Cloud does not have availability guarantees unless you buy into the upper tier. On the good news side, you should see your system back very soon. The worst outage I have seen on Cloud systems is 4 hours, 3.9 of which were caused by network providers rather than Cloud,

This says what it is - the Cloud system you are trying to use is going through some work that needs doing. Try it again later and you should find it is fine. Most Atlassian Cloud maintenance windows quote 30m, but last less than 10m. TLDR: Try again now, it should be fixed

Yes, start with an application link between the two, then start to look at what you want from "integrate"

You will need to make the page available in one of the spaces the customers can see.

The comments do not get copied during "clone" because they are a converstation about the original issue, not a conversation about the new cloned one. Cloning issues is for an edge-case where you need a copy, it's not for duplicating existing work. Cloning to turn test cards into bug cards is a broken process - you should…

Yes. If you would like more than just "it supports some https", you will need to expand on the question.

It is quite hard to answer this question because you have not explained what you expect from a "call back url" in Jira. When connecting Jira to another remote application, you usually have to define how that application works, so that Jira can understand how to talk to it. I would say exactly the same about the other…

Ok. If you want help, we kind of need to know where you are stuck or what the problem is?

In a listener, you get an "event" object you can work with. This contains a load of stuff you might need (the pre-event issue plus a list of changes are the most useful things generally). A very blunt answer to your question is just MutableIssue mi = (MutableIssue) event.issue It will grab the issue from the event and cast…

I think we need a little more explanation of this questions. You have used "Jira 13" in a way that implies you are using Jira 13, which would be difficult, as the latest version of Jira available is 8.5 Do you really mean "version" as Jira uses as a field? If so, that helps, but leads me to confusion about what you are…

I think you might mean that someone added a new option to the list of priorities? So that people editing or creating issues can now select what seems to be quite a silly looking priority (if it's a 1, surely it should be "critical", not "medium"? Or "trivial" if you order things in the opposite way) If I am right, then…

All tasks are created with a key, it's one of the few pieces of completely mandatory data, so I'm a little confused as to what the problem here is?

https://confluence.atlassian.com/adminjiraserver/configuring-an-smtp-mail-server-to-send-notifications-947184044.html covers it. If you want help from us, you will need to explain more though - "unable to add" - what are the symptoms and what do you think the "gmail account settings" are doing?

@ChrisR- "dislike" was available on the previous community platform and was seen as counter-productive. We wanted people to feel welcome and get them engaged. When it was used correctly (as in "this is a bad thing" or "I genuinely don't like your post because") it was ok. But most were being used to attack individuals, and…

Not quite "any time", more "review monthly", but you do not need to worry about the data, or going up or down. With both Cloud and Server versions of Atlassian software, you get all the functions and the licences are simply a "cap". You can jump from 10 licenses to 500 or drop from 500 to 10 without having to think about…

They can't be written like this because you are not telling Jira what to order by. Imagine you have 12 issues, six Done and six in other status. You've told Jira to order half of them one way and half another, but you have not defined an order for the list itself. A list can only have one sort order. There is actually a…

The "updated" field is calculated from the last time an issue had its data changed (project is one of the items that saves the date, along with all the fields, status, comments and so-on. From memory, it's only links that don't cause an update) On Server/DC you can use code or even amend the database if you must, but on…

If nothing else, just an indicator of how far behind you are and ideally, a date of next update.

Could you explain what you think "community" and "enterprise" editions are? 

8.x to 8.x should not be a problem. Read the release notes to check if anything big has changed, the api changes will follow that.

If you edit an issue, that will be written into the issue history. This is what issue trackers (should) be for.

The answer to that is above.

No. Either the resolution is null/empty (unresolved) or it has a value (resolved). "pending" would not be clear as to whether it is resolved or not, so you should not use it for this. "Not going to do this for a while" is fine, but it is a status, not the reason you are closing something. Move it into the workflow.

I am afraid it is not clear what you are doing or what you have done here. I think we need to ask you for more detail on what you mean by "Jira account". There are broadly three ways to access Jira on Cloud, none of which I could describe as a "jira account". (There is such a thing for Jira Server) Could you explain what…

This basically means the Jira server cannot talk to itself. This could be firewalls, network routing, unusual network config, and quite a few other things. The most common cause I see is, exactly as @Aleksandr Zuevich suggests, the SSL for Jira to see itself. If it is the SSL, then the usual cause is that while Jira is…