How to set an Epic date that cascades to all tasks?

[Deleted user]

I have created an epic: and I wonder if there is a simple way to communicate the new migration date in a way that it cascades to all tasks that have been created under the epic? Or is to include this information in the activity log in the epic and mention everyone involved the only way to do it?

[Nic Brough -Adaptavist-]

Can you get to Jira locally, without going through the proxy?  If you can, then it's a proxy error, if you can't, then start with a look at the Jira application logs to see where it is going wrong.

[Arch Fiend]

Hey Nic,

Thanks for replying. I'll see what I can do, looks like there is something wrong with the server as well. I'll update this thread asap.

[Arch Fiend]

Our System Administrator solved the issue for us, all he said was "wrong protocol between reverse proxy and backend. and a lot of other mess.". Hope this helps to anyone reading this thread :)

[Arch Fiend]

Got another update from our admin :)

- "There were 3 jira accounts (I have configured only one). And every account was pointing to its own instance. Nginx and me myself were totally lost where to proxy jira requests. So I had to remove all these accounts, instances, change ownership of jira files, and kept only one startup init file."

Any ideas as to what caused this?

[Nic Brough -Adaptavist-]

Sounds like you've installed it three times.