acsjira@honeywell.com Piotr's comment above states the cause.

Hi

What is the actual cause of this issue? We are facing this issue in some boards.

As the behavior is correct at the moment, we will be improving the error message in this case to notify the fact that a subtask is being included via the filter while excluding its parent.

Hi Mark,

As the support suggested: "Based on the error message, it seems that you have been hit by a known bug - GHS-6471.

This bug occurs when in a Sprint, a sub-task is included without the parents task. So, this means that only the sub-task is present in the sprint, but not the parent task.

This would cause the report to face the error that you are seeing."

It was correct. In our case it was enough to make sure that there are no subtask type issues (the filter is based on labels and I don't remember whether it was a Sub-task or Technical task that caused the malfunction) without their parent issues in the board filter.

I don't know if Atlassian is going to fix it any time soon.

Cheers,

Piotr

We have a board where this is occurring as well. The latest GreenHopper releases have not corrected the problem.

What is the correct resolution here? Will it be fixed in a future release of GreenHopper? Can you provide instructions for how to correct the problem here or should I open a problem report on support.atlassian.com to get resolution?

Thanks.

Thank you very much for your help.

Regards,

Piotr

Hi,

I have moved this issue to be handled under Atlassian Support and you can access the new issue created in the linked issues section.

We will provide you with our response in the new issue created. I am proceeding to close this issue.

Cheers,
Renjith

Thanks for reporting this issue. We would like to investigate further using your data set, if possible. A Support Engineer will soon contact you to create a support case where you can provide more information.