Upgrade attempt from Ubuntu 16.04 to 20.04 broke mail notifications and marketplace connections

[ilter]

Hi,

Yesterday, I backed up our Jira Server (v8.12.1) and tried to upgrade Ubuntu from 16.04 to 18.04.

During upgrade I got perl and apache version incompatibility errors and because of these issues, upgrade was cancelled.

After that attempt, restarted the server and checked jira modules and pages, and everything was working fine - was planning to revert back to the backup if that wasn't the case.

Today is monday, and people started using Jira, and I realized a message at the administrative pages in Jira.

"The Atlassian Marketplace server is not reachable. To avoid problems when loading this page, you can disable the connection to the Marketplace server. Click here for more information..."

Then I realized the mail queue and mails were stuck at the error queue.

No matter what I tried with the outgoing email test page, I couldn't manage to make notification emails work. So, it's too late for restoring from the backup since people started using Jira today...

I suspect that these issues arised because of the perl version installation during the Ubuntu Upgrade. I was asked to upgrade from a 5.22 version of perl to 5.26, and I said YES. After that, Apache version mismatch came up and didn't succeed (that was the error failing the upgrade).

Now I think that reverting back to the default Perl version that comes with Ubuntu 16.04 may fix that issue.

Do you have any comments about the idea of Perl downgrade? Would it work?

I am down for a new server installation and upgrading to the latest version of Jira on a new box, but need to fix that too, until I manage that.

Thank you for your comments!

[Nic Brough -Adaptavist- · Accepted solution]

Same as you change it to any other workflow.

When the workflow was simplified, Jira Agile created a new workflow scheme for it and set that on the project. All you need to do is go to project administration and change the workflow scheme to whatever one you want to use instead of "simplified"

[CoffeeMate]

Hi Nic,

Thanks for the reply. I just found an article and changed the workflow.

However now in the Agile board, in both of Plan and Work views, almost all issues are gone. Only one issue that was in progress is remained there.

How can I fix this?

[Nic Brough -Adaptavist-]

Sounds like your boards no longer include the status that are in the workflow you've moved the project over too. The boards won't change to match the workflow automatically (because there's no real way Jira Agile can know what you really want to end up with)

Go to the Agile Board and reconfigure the columns.

[CoffeeMate]

I updated the board and reconfigured the columns.

Now some Open issues cannot be moved to the In Progress column. They can only be moved to the next two columns that are for Resolved and Closed issues.

EDIT: Even though the issue (a Task) has a status of Open, in the issue page, there's no Start Progress button.

[Nic Brough -Adaptavist-]

Your non-simplified workflow doesn't have the transitions that allow those moves, or, if it does, they have conditions that are stopping you from doing it.

You'll need to read the workflow to work out what is going on.

[CoffeeMate]

Hi Nic,

Thanks for the reply. I just found an article and changed the workflow.

However now the Agile board, in both of Plan and Work views, almost all issues are gone. Only one issue that was in progress is remained there.

How can I fix this?