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; } } }

Graphical issues in Jira Automation

Roman Holdener

In our productive Jira Service Desk Instance (Version 3.4.2) as well in our test environement (Version 3.16.4) there are sometimes graphical issues in Jira Automation. Sometimes the "IF" block is covered by the "THEN" block and therefore not usable (examples see below). This happens on different clients using Chrome, but also in Internet Explorer. Changing the Zoom in the browser doesn't have any effect on this behaviour. This already happened a while ago, but eventually, the problem disapeared. Now it happened again.

Screenshot 1: An IF-condition is already there. Here the box is partly covered by the THEN

Screenshot 2: A new Automation without any IF-conditions. The "IF"-box is completely covered by the "THEN"

Does anyone have any Ideas how to solve this?

Accepted answers

Angélica Luz

Hi Roman,

Welcome to Atlassian Community!

I searched for this issue and found only one ticket where this issue was caused by an add-on called HolyDev Environment Manager. This issue is from 2017 and I saw that this add-on changed the name to Golive | Test Environment Management.

I see that this add-on is installed on your server and maybe this is causing the bug. Can you disable the add-on and test the automation again?

Please, give it a try and let us know how it goes.

Regards,
Angélica

All comments

Angélica Luz

Hi Roman,

Welcome to Atlassian Community!

I see that this add-on is installed on your server and maybe this is causing the bug. Can you disable the add-on and test the automation again?

Please, give it a try and let us know how it goes.

Regards,
Angélica

Roman Holdener

Hi Angélica

Thanks a lot for your reply. I could verify this. After disabling Golive, the automation did behave as expected.

Was there any solution to the ticket in 2017 other than disabling the plugin?

Regards,

Roman

Angélica Luz

That's awesome! I'm glad that I could help.

I found only one ticket where this issue happened, and the resolution was to disable the add-on. The customer who reported this issue was not using it anymore.

If you need to use the add-on, I believe that the best option is to contact their support to inform the issue and check if they have any workaround. You can click on the link on my previous answer and click on Support to find the link to create a ticket or to send an email.

Roman Holdener

Thank you. I contacted the support of Apwide yesterday. They weren't aware of the problem yet, but they fixed it right away and relesed a new version to the marketplace. Now everything works as it should.

Thanks a lot for your great support!

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-service-desk

jira-service-desk-server