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

Green hopper drag and drop changes not saved.

Tarun Sapra

Hi,

I am able to drag and drop the issues in planning board in greenhopper, but once I refresh the screen the changes are gone and the issues are back to their old position.

Version 5.8.7

In the project configuration Rank field is also added and it was working few days back but suddenly has stopped working.

Please suggest. Thanks.

Accepted answers

Tarun Sapra

The problem was with the ranking field and database inconsistencies, it was fixed after jira upgrade to 5.2.11

All comments

AhmadDanial

Hey there, Tarun.

Have you checked whether the user is allowed to make the transition via the Conditions in the workflow?

Do you have any scripts running in your instance? Try to disable them and replicate the problem again.

In addition to that, can you please try and clear off your browser cache as well?

Warm regards,

Danial

Tarun Sapra

Hi Ahmad,

I am talking about planning board, so workflow conditions don't come into play, as they are in task board. Yes i cleared the cache. No there aren't any scripts running as such. I have raised support ticket for it.

Igor Sereda [ALM Works]

Hi Tarun,

Do you by chance have Structure plugin installed? If yes, please check if any structure has a GreenHopper synchronizer installed, by opening Structure | Manage Structure, viewing a list of all structures and checking Sync With... column. GreenHopper synchronizer can limit the possible changes to the order of issues.

Please follow up if you need further assistance with GreenHopper synchronizers.

Igor

Tarun Sapra

no, I don't have structure plugin installed.

AhmadDanial

Hey there again, Tarun.

Hopefully the Support Engineers will be able to provide you with the help that you need. Sorry couldn't be much help.

Warm regards,

Danial

Tarun Sapra

The problem was with the ranking field and database inconsistencies, it was fixed after jira upgrade to 5.2.11

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-software