Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Due date not ending after close user story #182

Open
Fvcosta2023 opened this issue May 1, 2023 · 1 comment
Open

[BUG] Due date not ending after close user story #182

Fvcosta2023 opened this issue May 1, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@Fvcosta2023
Copy link

Fvcosta2023 commented May 1, 2023

Describe the bug

Even when a user story is moved to a completed status, the due date continues to count, with the notification colors advancing, until the overdue mark.
When a user story is completed or archived the due date should end, right?

How can we reproduce the behavior

Set a due date with a deadline of one day. At the same doa move it to completed.
The next day they will be completed, but with the delivery date already marked as late (zero days to the end)

Workarounds

N/A

Screenshots

Taiga environment

Self-hosted Taiga in Docker. No log errors.

Desktop (please complete the following information):

  • OS: <Windows 10] -->
  • Browser: <Chrome,>
@Fvcosta2023 Fvcosta2023 added the bug Something isn't working label May 1, 2023
@Fvcosta2023
Copy link
Author

Atraso
Icon of due date counting after closed user history

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant