Robert Wen_Cprime_ Community Champion

Your list appears to be in the correct order. For more details, here's a guide from Atlassian: https://confluence.atlassian.com/adminjiraserver/upgrading-jira-applications-938846936.html

Do you have default values if the custom fields aren't set? e.g. issue.customfield_10136 should be 0 if not set and issue.customfield_10135 should be 1 if not set.

How about having a look at this Getting Started guide from Atlassian which talks about creating Spaces, a page hierarchy, and setting up permissions? https://www.atlassian.com/software/confluence/guides/get-started/set-up#step-1

How are you defining the new field? Are you using a plugin like Scriptrunner which allows you to define calculated fields?

This sounds like you're keeping the database where it is (the DB is separate from Confluence?) Overall this looks like a good plan.

I get the installer manually by attaching the command through cURL. curl -L -O https://www.atlassian.com/software/confluence/downloads/binary/atlassian-confluence-7.13.0.bin If that fails, you'd have to go to the URL using the web browser on your server, and find the version and download the installer. 

If you have to stay on Confluence server for a long while, I would recommend upgrading Confluence first so you have a better migration path to Cloud. Detailed upgrade guide is here: https://confluence.atlassian.com/doc/upgrading-confluence-4578.html Hope this helps

What role do your team members play? If they're all Viewers, they can't be assigned issues.

As far as #1 is concerned, JCMA will not migrate Jira Service Management projects (as you have found out.) Your only recourse is to use Jira Site Import.

It could be that for this particular project you don't have the "Add Comments" permission. You'll have to talk to your Jira administrator to sort that out.

You should be OK. Deleting a project doesn't delete its configurations (e.g. what schemes it uses).

This looks like you followed the directions for connecting with the Server (aka "on-prem") version of Jira as opposed to Jira Cloud (SaaS). There appears to be a Marketplace app for Sentry. Link is here. https://marketplace.atlassian.com/apps/1219432/sentry-for-jira?hosting=cloud&tab=overview Let me know if this helps.

According to the supported platforms page, Linux distributions and versions are pretty broad. The only time I would see about upgrading the OS would be if you need to switch from 32-bit to 64-bit. What is the current version of CentOS and Confluence you have now?

We talked about the original exploit in this thread: https://community.atlassian.com/t5/Confluence-questions/No-access-to-Conlfuence-Webpage-100-CPU-usage-from-quot-dbused/qaq-p/1793393?utm_source=atlcomm&utm_medium=email&utm_campaign=immediate_general_answer&utm_content=topic In it, one of the Community members gave some…

The notice doesn't apply to 3.5.2 only because it's well past its End of Life (EOL) date. You may want to look at upgrading Confluence. Be warned, though, you'll probably have to do some intermediate upgrades to get to the most current version (7.13)

Without knowing more details of what you did, I'm not sure I can advise anything more than possibly restoring the installation, attachments, and database from backup.

I'm not following. My impression is that Confluence failed to upgrade. You're still on 6. Are you not?

According to the docs here, if you're on the free level, issue-security level is not available to you. https://support.atlassian.com/jira-software-cloud/docs/manage-how-people-access-your-team-managed-project/

Have you looked at this app on the Atlassian Marketplace? https://marketplace.atlassian.com/apps/1223972/geodata-for-jira?hosting=datacenter&tab=overview

Here's a pretty comprehensive checklist of things you should look at for your upgrade process: https://confluence.atlassian.com/adminjiraserver/upgrade-checklist-966063320.html

According to the system requirements for Confluence 7.13, your MSSQL needs to be at least at 2016. You should upgrade that before upgrading Confluence. https://confluence.atlassian.com/doc/supported-platforms-207488198.html

The customer will only see the JSM ticket (SR). If it is linked to a Jira Software ticket (CR) they will not be able to see it on the portal.

Subscriptions and instances are on the billing page on admin.atlassian.com. These instructions should guide you to canceling and deleting (if you have the new UI) instances. https://support.atlassian.com/subscriptions-and-billing/docs/cancel-your-site-subscription/

Here is the landing page for Confluence documentation, including videos and online documentation. https://www.atlassian.com/software/confluence/guides

Hiding a project was an old way of archiving the Jira project before project archiving came on the scene. This knowledge base article demonstrates how its done: https://confluence.atlassian.com/jirakb/archiving-a-project-in-jira-server-950287459.html

Instructions for doing the setup of a customer portal account are here: https://support.atlassian.com/jira-service-management-cloud/docs/add-a-login-message-in-your-help-center/

You can see others' tales of woe in this question: https://community.atlassian.com/t5/Confluence-questions/No-access-to-Conlfuence-Webpage-100-CPU-usage-from-quot-dbused/qaq-p/1793393?utm_source=atlcomm&utm_medium=email&utm_campaign=immediate_general_answer&utm_content=topic Steps included: - Shut down confluence - Apply…

The way to do this is permissions. License is determined by membership in the Product Access group (usually "Jira-service-desk-users"). To remove the ability to assign a person to a JSM issue, for that particular project's permission scheme, see how "Assignable User" is laid out. You may need to remove that user from the…

You may want to try rebuilding the indexes. Instructions are here: https://confluence.atlassian.com/confkb/how-to-rebuild-the-content-indexes-from-scratch-833941594.html

no email support, but you reach Atlassian Support through https://support.atlassian.com/contact/#/