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

Due date shown on jira next-gen board does not match the due date on the issue itself

Kyle_bbm45q

Has anyone else noticed this?

I have a Jira next-gen project with a kanban board.

I create an issue and set the due date to August 10, 2019 (which is displayed as 2019/08/10). Close the issue detail view.

The card on the board shows the due date as Aug 09 - instead of Aug 10.

as seen on the issue itself:

as seen on the board:

Accepted answers

Kyle_bbm45q

I submitted this to Atlassian support and it is a known bug in Cloud next-gen boards identified June 19, 2019. Watch this bug report if you want to follow it:

https://jira.atlassian.com/browse/JSWCLOUD-17961

All comments

Ollie Guan

Hi @Kyle ,

Have you tried to modify the value of the expiration date again, and the values in these two places are still inconsistent after the update?

Kyle_bbm45q

Yes. When I update the due date on the issue, the date on the card also updates but is still a day off. I am using a next-gen kanban board.

I did some more testing and found that this is only a problem on my next-gen board. On a kanban board showing issues from a normal Jira project the due date on the issue is accurately shown on the card on the board.

Ollie Guan

Hi @Kyle ,

If you create a new issue, will there be different due date at these two places?

I tried to test in my next-gen project, but I didn't find a similar situation.

Maybe you can try rebuilding the index to see if it can be solved.

If it still doesn't work, please contact the support team.

https://support.atlassian.com/contact/#/

Kyle_bbm45q

Yes, every issue I create new or old has the difference in due dates between the issue view and the kanban card view.

We use Jira Cloud which doesn't have a reindex option.

Thanks for your suggestions, I am opening up a support ticket with Atlassian.

-kyle

Kyle_bbm45q

I submitted this to Atlassian support and it is a known bug in Cloud next-gen boards identified June 19, 2019. Watch this bug report if you want to follow it:

https://jira.atlassian.com/browse/JSWCLOUD-17961

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud