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 Agile - Create Sub-task -> Board does not refresh automatically

Florian Zink

Hi everyone,

my JIRA instance is running for 1month now without any restart. A user told me today that since a few days, the agile boards (SCRUM) don't refresh automatically anymore when he creates a new sub-task in the issue detail view screen.

Instead after creating a sub-task, a message appears that says:

Your sub-task ABC-123 has been created but is not currently visible

He says if he waits for ~60 seconds and refreshes the the site himself (by pressing F5), the sub-task appears under the parent issue on his board. The Board filter has not been changed.

Has anyone experienced something like this before? I tested it on my staging environment and there the automatic refresh still works.

We are running JIRA 5.1.5 and Agile 6.3.2.2

Are there any caches that could be full or do you just need to restart JIRA from time to time (like windows) ?

Thanks in advance!

Cheers

Florian

Accepted answers

All comments

Andy Nguyen

Hi Florian,

Are you mentioning Plan mode or Work mode? The warning message you show will only appear when you create sub-tasks in Plan mode as sub-tasks are not to be displayed in this mode. They are actually created but only listed in the Issue Detail View of their parent issue. If you create sub-tasks in Work mode, however, there will be no such warning message and the sub-tasks are visible in To Do column (default).

Hence I think that your user tried to create a sub-task in Plan mode and then he was able to see it in Work mode. There is no such thing like refreshing the site and then the sub-tasks are visible in Plan mode. For more information, kindly read Using Plan Mode.

Cheers,

Andy

Florian Zink

Hi Andy,

sorry, but I am talking about Work mode. I tested it again today, see screenshot.

Cheers

Florian

Florian Zink

Hi Andy,

sorry, but I am talking about Work mode. I tested it again today, see screenshot.

Cheers

Florian

Florian Zink

Hi Andy,

any ideas what could be the problem? Is it something a simple restart of JIRA would solve?

Cheers

Florian

Andy Nguyen

Hi Florian,

I haven't been able to reproduce your case. It seems that there exists a constraint that prevents a sub-task from being automatically shown upon creation. Would you please review this article for possible causes and corresponding resolutions: Issues are not appearing in GreenHopper Rapid Boards.

By the way, can you provide me with the board's filter query as well? You can also try re-indexing and restarting JIRA to see whether the issue can be resolved.

Cheers,

Andy

Andy Nguyen

Hi Florian,

I can finally reproduce your case. Please have a look at the following screenshot:

By default, when you create a new issue or sub-task, the status is automatically set to be Open. Hence, if you do not map Open status to any columns in your agile board, the created issue or sub-task will not be visible upon creation. It will only become visible when you change the status to whichever is mapped to one of the columns.

Hope this is actually the cause of your issue.

Cheers,

Andy

Florian Zink

Hi Andy,

thx again for your help. Sadly though, your findings do not apply to my scenario

The "Open" status is correctly mapped to the appropriate column (in my case, the "To Do" column).

I also read your link about "issues are not appearing in GreenHopper Rapid Boards" but none of these causes apply to my JIRA instance.

I restarted my instance last weekend, but sadly that didn't fix the problem either. Should I try to reindex at least the issues that are displayed on the board? Or does JIRA automatically reindex when it is started?

Cheers

Florian

Florian Zink

Hi Andy,

just a short info update:

I edited the JQL for the board filter and removed a JQL tricks function that was being used and instead now use a Script Runner function from jamie. My colleague says now at least the wait time has reduced to ~3 seconds.

Cheers

Florian

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-administration