sub-task card shown in the wrong column after drag

[Alessandro Tondo]

If I drag a sub-task card in a different column, it often happens that Jira updates its state correctly (i.e. in the issue panel the issue status is right), but the kanban board still shows the sub-task in the previous column. From the kanban board I cannot drag it in the state where it actually is (as it should be), neither in the state where it is shown (but this transition can be performed with the button in the issue panel).

Moreover, if I perform the backward transition to the initial state from the issue panel, in the kanban board the relative card swaps to the previous state column.

Example:

• Drag sub-task from Open to In Progress: still lays in the Open column, but actual status is In Progress.
• Click Suspend Progress in the issue view and back to board: sub-task card lays in the In Progress column, but actual status is Open.
• Continue with this behavior...
• I don't know when the sync is triggered, but after a while I can see the card in the proper column.

[Fabio Racobaldo _Herzum_]

Hi Alessandro,

I think that you need to correctly setup columns in your kanban board. A column could contain more than one status of your workflow so that you have your cards in the same column even if your card status has been changed.

 Here more information about how-to setup your columns https://confluence.atlassian.com/agile/jira-agile-user-s-guide/configuring-a-board/configuring-columns

Hope this helps,

Fabio

[Alessandro Tondo]

Hi Fabio,

I'm sorry if I've not explained it well, but the statuses are correctly mapped in their relative columns. Indeed, normal issue types work like a charm, and after some time, also the sub-tasks lay in the right column.

Nonetheless, immediately after the drag-and-drop action, sub-tasks seem not to change their column.

Thank you for your patience and understanding.

[Fabio Racobaldo _Herzum_]

Hi Alessandro,

np. It's a very strange issue. Are you able to identify the time in which your subtasks are in a not correct column?

Does the problem appear even if you refresh the board? Did you check the indexes?

Ciao,
Fabio

[Alessandro Tondo]

I've already tried to refresh or reindex, but nothing changes (at least not immediately). The problem is that it happens randomly, not at every transition.

I try to collect more details and I'll let you know.

Thanks for your time.

[Alessandro Tondo]

I haven't got this issue since my last update, or at least I haven't seen it happening.

However today I've faced it with a default issue type (i.e. not sub-task as said in the first post). Here are few screens to let you understand better:

As you may understand, SWROS-26 should lay in the "Waiting for Review" column as shown in the summary on the right, but after the transition by drag-and-drop from "In Review" to "Waiting for Review", it has not changed the column together with its state.

And by drag-and-drop I can only move it to the last column, i.e. "Closed", but not again in the "In Review" column.

Nothing changes with reloading and reindexing.

[Fabio Racobaldo _Herzum_]

Hi ALessandro, 

please could you show me the column configuration?

[Alessandro Tondo]

Here you are:

Is there anything wrong? (Analyzed and Treated states are relative to another workflow not yet used)

[Fabio Racobaldo _Herzum_]

Hi Alessandro,

reviewing your configuration (that seems ok), I don't understand why SWROS-26 appears in the column "In Review" even if its status is "Waiting for Review" that should be mapped into "Waiting for Review" column.

In my opinion there are some issues at index level.

Please, perform the following steps :

1. System -> Integrity Checker
2. System -> Indexing -> Reindex

After doing that, please provide me a feedback about board and issues.

Ciao,

Fabio

[Alessandro Tondo]

Unfortunately I had to close that issue a couple of days ago because this problem it's happening on a production server.

I'll check it when (if) it happens again.

Just for info, I had already tried to reindex without solving the problem, but I remember several Lucene errors in the past. However no one in the last weeks.

Anyway, thank you for your time.

[Alessandro Tondo]

Hello Fabio,

It happened again and this time I've checked the instance health report. It was showing a Lucene error again, but this time reindexing has solved the issue.

What can I do to avoid these errors?

[Fabio Racobaldo _Herzum_]

Hi Alessandro,

there're many causes that could cause this issue. Please, check the following article in order to perform a first check :

• https://confluence.atlassian.com/kb/health-check-lucene-index-files-location-873918046.html
• https://confluence.atlassian.com/jirakb/jira-applications-performance-tuning-229179856.html (section Index Optimization)

Ciao,

Fabio

[Alessandro Tondo]

Thank you Fabio, I really appreciate your help.

I have a look as soon as possible and I let you know.