Nic Brough -Adaptavist- Expert

I can't tell if that's a problem that needs to go to Microsoft, your admins who look after your MS accounts or Atlassian. I'd start by raising it with Atlassian though, over at https://trello.com/contact - use the last option on the form "contact support"

The problem is that there is no equivalence. Basically, if you're looking for Cloud docs, stop searching the server/DC docs, and vice-versa.

You don't. You have no access to the database on Cloud. However, your question is very vague - what "list of values" are you looking for?

Are all three collation settings correct on your database? How did you perform the upgrade on your data?

This is not "certain roles can create issues", it is "certain roles are the only ones able to create certain issue types" Jira does not do that natively, the create-issue permission is done at project level, not issue type. You could do it in Behaviours in Scriptrunner, but that would only affect the web-UI and isn't too…

Automation does not have a function to move issues between projects. Moving an issue is a complex process that changes the structure of an issue, and as such, you have to check that it is possibble, and usually ask the user to add or amend data on it, and confirm that they understand some data may be lost. It should never…

This isn't going to work Scripted fields are not enterable, they are calculated Reporting and searching is not going to be reliable, unless you re-index, or at least view, every issue with your scripted field on it every day just after midnight. 

Correct, the sprint has to gather the starting point of a sprint when you create the sprint. If you change estimation part way through, it's got no way of calculating anything. And for old sprints, they were completed using a different estimation statistic, so it can't report on them because it didn't use the current…

Team managed projects don't use Epic Links (yet)

Welcome to the Atlassian Community! It's annoying that the button appears even when a user has no access to create anything, and there's a request to get it fixed somewhere. But you can't remove it on Cloud. It's harmless - it won't let them do anything, but it should really follow the Atlassian standard of not offering…

On an uninfected clean machine? Using a new download from a non-infected source (i.e. Atlassian)?

So have you installed a new download on a clean machine, and restored data from a pre-virus attack backup?

Ah, I see. The way to handle it in a reasonable way is to roll it all over to the next sprint. Anything else destroys your reporting and estimation capabilities.

Welcome to the Atlassian Community! No. A lot of apps provide functions in ways that can't be limited to projects, and even for those that could be limited to projects, Jira doesn't support per-project installs. There are some apps which have project-specific configuration though, you'd need to look at each one to see if…

Yes, via Atlassian Access.

The answer does depend on what you mean by "document". If you mean "document = page", the way a wiki like Confluence is supposed to be used, then yes, there are loads of ways of looking at the metadata for a page - macros, reports, page lists, searches, all expose different bits of the metadata. If you mean "document =…

Part of the problem is not that a feature "doesn't exist", it's a feature that "has been done so differently, the docs for one really don't apply well enough, and we've restructured it all". It happens a lot for the older docs for versions that are no longer supported, they're always refactoring later documentation.

Jira's licence/subscription tiers are shown at https://www.atlassian.com/software/jira/pricing and when you buy apps for it, they have to be licenced/subscribed-to at the same number of sers. No, we're not using an app directly for the migration, a backup of Cloud can be restored to Server/DC surprisingly easily. (We're…

I think we've missed an update there, Next-gen should have been changed to team-managed ages ago. There's nothing for you to adjust, but do check that project AB is definitely a Company Managed Project and also that you've not got any Team-managed Epics it might be looking for.

Post-functions and fields are a couple of aspects of coding for Jira, extending past its built-in functions. The REST API is a bit more generic - a lot of systems use a REST API to allow other systems to talk to each other. The sentence there looks like it may have lost a little when being translated from what a Jira admin…

You won't find it in the database - the whole point is that the data can't be written to it. You've got a custom field or script or app that is broken.

Welcome to the Atlassian Community! I'm afraid that tells us nothing about what you are doing or what the problem is. Any error messages? Are they in Bitbucket or Sourcetree? Why are you running Bibucket on your development machine rather than as a service, on a non-standard port?

Welcome to the Atlassian Community! Accounts do not have these properties, the services do. Your whole system is paid/free/premium/standard, not the accounts using it.

Sorry, true, yes, TMPs can't do this. Only CMPs can use Epic link to do it.

Welcome to the Atlassian Community! Those are alphanumerically sorted. If you want them sorted by partial alpha and then numbers held as strings, you need to use leading 0s - I-001, I-002, I-011

It's the same answer.

I would add that there's a fundamental problem with this part of it: >a Team scrum board for the different Project members Boards have a strong equivalence with Team (heck, Jira Align actually defines "team = those using a board"), so you wouldn't normally want to create many boards for different parts of a team.

That is correct, you should not be sharing keys across accounts.

System workflows are there as demonstration and building blocks. They cannot be removed.

Um. >how to handle this unfortunate, and sometimes unavoidable circumstance. It's not in the slightest bit unavoidable. You shouldn't be doing it. Changing the estimate on an issue denigrates what the team have been doing, and destroys your reporting and estimation system.