Nic Brough -Adaptavist- Expert

This won't be affecting your upgrade - you can upgrade to any version released before 29th June with this licence. To find out what is going wrong with the upgrade, you'll want to read the logs (confluence home/log/atlassian-confluence.log is the main one to start with)

No, you can't do this with labels. It's pretty much the opposite of what they were designed for. The functionality you describe can be done though - create a custom field of type "select" - you can control the list of options and only allow one to be used (if you want to select many, use a multi-select)

I'm afraid we can't help you here. We're all using Atlassian systems, but we're not the Mojang administrators and I don't know if any of them are active in the community and hence might see this post. I'm afraid we're stuck - you need to talk to Mojang.

You should simply merge the two existing scripts into a third: return (output of number of issues script / output of total cycle change script) Note that the other option people may think of here is to calculate the third field from the first and second - do not do that, as fields are not always calculated in the order you…

If neither log shows any logging of an error or a shut-down message, then either the log was unwritable at the time of an error, or something or someone killed the process. There is no other way to get into this position.

Post functions only run on transitions, and you spoke in terms of edit, not transition. If it is a transition that is doing it and the resolution field is not on a screen, then yes, there's a post-function setting the resolution.

Could you try editing the filter so that it returns fewer issues? Ideally less than 1,000

You'll need to rethink what you mean by "complete" and make sure it ends up in the last column on the board.

No, the reports are supposed to be showing the current data. If you want to keep snapshots, you'll need to copy the current display or data to somewhere else.

https://marketplace.atlassian.com/apps/1210932/cute-for-jira?hosting=server&tab=overview may be worth a look for you.

If you remove the new swimlane from the board, does the issue appear in the "no swimlane" area at the bottom of the board?

My guess is that you have included the resolution field on the issue edit screen (and/or the create issue screen). You should remove that from the screen, then the resolution won't get set by editing and hence no strike-out

You have not told us what the problem is here. Admins can remove anyone from any of the settings, except for the last one - it won't let you "orphan" the account.

An inexperienced admin has added the resolution field to the create issue screen. You need to remove it - go to admin -> issues -> screens, or project admin -> screen scheme, and find the one where the error has been made

Boards do not contain issues, they select a list to show. There is no "choose to put it on a board", you put data on an issue that is then selected or not by any board. You will need to look at how each board selects their issues to allow your user to understand which boards it will appear on depending on the data they put…

The atlassian.net on Atlassian Cloud systems cannot (yet) be changed.

This is a limitation of the php-jira-rest-client - as far as I can see, it has no way to identify fields other than "your user has to know the ids of source and tartget"

You'll need to look at the SMS service provider you have set up to work out how to tell it to stop.

First, look at the application log (jira home/log/atlassian-jira.log) - what does the last chunk of it say? It sounds like you've looked for some errors, but if the application was stopped correctly, it should show shutdown messages, and if it failed, there will be an indication of why. Second, check the service log to see…

There is no download needed to use Jira Cloud (unless you don't have a browser), so I'm very lost on what you are trying to do. What have you actually downloaded and what installation documentation are you trying to follow?

That defeats the purpose of having a backlog. So go to project settings -> features and turn it off, as you don't need it.

No, there's no way to do that on Cloud.

Your existing 250 user licence will be accounted for in the price - if, for example, you have 250 users that will expire in December this year, your 500 user licence cost will be reduced by the cost of 6 months of a 250 user licence.

What are you using to create the subtasks and how is it configured? (explain dOd - to most of us, it's an acronym for "definition of done" which is nothing to do with subtasks other than defining how they should be closed)

What is the difference between an issue that went into the new sprint and one that did not?

There is no issue here. It deletes the email to prevent it being reprocessed and creating a new issue every time it checks the incoming mail.

Filters don't belong to projects so the question does not make sense. (Think of it this way - if you deleted every project, every saved filter you have would still be there. Looking for issues that are not there, yes, but they would still exist) Could you explain what you mean, bearing that in mind?

You would need to write an app that can detect new requests and pick a random assignee. You may be able to do this with one of the scripting apps available to Cloud (I usually suggest automations as well, but I do not think there is any way to do randomisation in automations). But I would also echo Jack's comment about…

I am sorry, I've just noticed I missed something. In your screenshot, you show us only part of the dropdown - could you scroll to the top? In most cases the "system" fields are listed before custom ones.

Look for the "supported platforms" document for each application, they'll give you everything you need to know.