One of my Jira projects has recently developed a weird bug on the Kanban board, in which tasks in the first column are all grouped together at the bottom of the column. No matter what I do, tasks will not stay at the top of the column -- they always drop to the bottom, forcing me to scroll down to see them. This creates the risk of tasks being overlooked & forgotten.
Tasks in the other columns are all grouped at the top, as they should be.
I have done some simple experiments to try and get to the bottom of this, and I have observed the following:
If anyone can offer some advice on how to remedy this problem, I would be very grateful.
Thanks & Regards,
Brendan.
Update:
I have just noticed that the same problem is occurring on one of my other Jira projects. Therefore the problem is not confined to the one project.
Problem resolved itself overnight without any intervention on my part.
Any future occurrences of this bug will be raised with Atlassian tech support.
Can you provide some screenshots of any of your board and the configuration.
Also the quik-filters and or other options that have an impact on the board visibility
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Here is a screenshot of typical Kanban board showing the behaviour I described. In some cases the tasks in column 1 can be completely off the bottom of the screen:
Below is a screenshot of the configuration screen for the above Kanban board. I am using the default settings (i.e. no custom workflows). The most I have done is tweak the column names & add an extra column to the board:
I'm not sure what a "quik-filter" is, but I am not using any filtering on my board. I did try filtering by Epic & team member once to see what would happen, but it made no difference.
Regards, Brendan.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm not able to reproduce this, I use Chrome.
The only things you could try first is to clear all cash and cookies and see how it looks.
Otherwise I do suggest to raise you issue at Atlassian support so they can check logging, to check what is wrong in your instance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Some good news. When I opened my Jira project this morning, I found that the problem had gone away overnight. Not sure how this happened -- I didn't have the chance to clear the browser cache or cookies before the problem went away.
Thanks anyway for your suggestions. If the problem occurs again I will contact Atlassian support.
Best Regards,
Brendan.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Update: I have just noticed that the same problem is occurring on one of my other Jira projects. Therefore the problem is not confined to the one project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.