JIRA 7.2 to 7.4 upgrade, forms are not editable

[aaron_deforest_du]

There are a couple of strange things that are happening after I upgraded from 7.2.6 to 7.4.2. 1) I cannot type in the comment textarea when leaving a comment. 2) I cannot type in the description textarea when creating a new item. 3) Sometimes the app just spins forever after hitting the create button. 4) I don't see anything on the dashboard anymore. My user only has the default dashboard, and I only tried the default dashboard. -- For this upgrade, I cloned my production instance and database to my text network. Any ideas why this could be happening? Cheers, Aaron

[aaron_deforest_du]

Yes.  The javascript seems broken.  When I watch the web console, I see that some content was blocked because my connection was to https://jiratest but proxed to/from http://localhost:8080.

I happen to be doing a test upgrade of Confluence at the same time.  That upgrade was fine, but complained about reverse proxy stuff.  I found some Confluence guides on updating the reverse proxy which worked well.  I applied this same information here, and it did the trick.

I added this to my server.xml, <Connector tag:

proxyName="jiratest" proxyPort="443" scheme="https"

And I updated my apache virtual host to look like the following:

ProxyRequests Off
ProxyPreserveHost On

<Proxy *>
        Require all granted
</Proxy>

ProxyPass        / http://localhost:8080/
ProxyPassReverse / http://localhost:8080/

<Location />
        Require all granted
</Location>

Restart both services.  Now I get the default dash board.  I can create items.  I can edit items.  Etc.

[Nic Brough -Adaptavist-]

It sounds like broken javascript, but I'm not sure how you'd break it on a simple upgrade.

You say "For this upgrade, I cloned my production instance and database to my test network." - I assume that means you then ran the installer and selected upgrade against this cloned system?   Were there any warnings or errors in the logs from the upgrade?

Is it possible to install 7.4.2 on your test system again, in a different set of directories against a different, empty, database, so you get a new system.  Does that show the same symptoms?