-
-
Notifications
You must be signed in to change notification settings - Fork 182
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
[14.0][FIX] s_a_promise_release: Reset last_release_date on unrelease #873
base: 14.0
Are you sure you want to change the base?
Conversation
@TDu Can you fwd port to 16.0 ? |
@TDu A little test should be welcome |
This PR has the |
self.filtered(lambda pick: pick.need_release).update( | ||
{"last_release_date": False} | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be on the move otherwise if you unrelease the moves, this won't be triggered.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have updated the fix
6d59ec2
to
3c8b989
Compare
@TDu Could you rebase ? |
When a transfer has been unreleased the `last_release_date` is not reset. This breaks the counters and the list of records (To Release, To Do) on the related channel.
3c8b989
to
9420b62
Compare
When a transfer has been unreleased the
last_release_date
is not reset.This breaks the counters and the list of records (To Release, To Do) on the related channel.
Now with this change the field name/label is incoherent...