nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

jira SD 4.3.2 return to old version of customer portal

Артем Подкорытов

How can i return to old version of customer portal?

In new version problems with approves (approve form didn't open, approve and decline bouttons not shown in form), and errors while create issues (check issue field, but all fields are filled normal)

Accepted answers

Yevhen Rohovets

Good day,

This is a bug of the new version of the service desk. We sent a support request and after some emails, Atlassian created this bug https://jira.atlassian.com/browse/JSDSERVER-6498

If you have access, then you can parse access and change translations in the service desk in .jar files

If the option now to fix this bug through transfers does not fit, then you need to completely install the new desk service and restore data from the previous version from the backup

All comments

Amith Mathur {Appfire}

Hi @Артем Подкорытов ,

There is no way to return to the earlier version of JSD once the JIRA/JSD has been upgraded. We need to check what error messages you are getting when you are performing approve/decline etc actions.

Thanks,
Amith Mathur

Артем Подкорытов

when a user in the portal goes to "my assurances" and tries to enter one of them - no errors occur. The form simply does not open. And the "approve" and "decline" buttons are not displayed. The only way a user can click a button is through the button in the email

Артем Подкорытов

errors while create issues (check issue field, but all fields are filled normal)

- set date format in system-advanced settings and system view to default value solve this problem

Артем Подкорытов

Yevhen Rohovets

Good day,

This is a bug of the new version of the service desk. We sent a support request and after some emails, Atlassian created this bug https://jira.atlassian.com/browse/JSDSERVER-6498

If you have access, then you can parse access and change translations in the service desk in .jar files

If the option now to fix this bug through transfers does not fit, then you need to completely install the new desk service and restore data from the previous version from the backup

Артем Подкорытов

Thanks will vote this issue

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-service-desk