Resolve "Automatic plan update fails because of missing version object" #527
No reviewers
Labels
No labels
Security
TeX
auto-update
board
done
board
ready
board
todo
check
delete-eslint-rc-js
check
update-builddeps-package-json
check
update-eslint-rc-js
check
update-gitignore
check
update-merge-request-template
check
update-prettier-ignore
check
update-pyproject-toml
check
update-renovate-json
check
update-tox-ini
part
backend
part
ci
part
docs
part
frontend
part
i18n
part
non-technical
part
packaging
prio
1
prio
2
prio
3
release-mr-5.x
size
large
size
medium
size
small
source
customer
source
customer::fsmw
source
customer::fss
source
customer::teckids
source
downstream
type
breaking
type
bug
type
feature
type
refactoring
workflow
blocked
workflow
confirmed
workflow
current-todo
workflow
discussing
workflow
new-app
workflow
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
aleksis/AlekSIS-App-Chronos!527
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "159-automatic-plan-update-fails-because-of-missing-version-object"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #159
assigned to @hansegucker
added 2 commits
d105fdb3- Don't fail on non-existing version object on automatic plan update5eecb018- Update changelogCompare with previous version
marked this merge request as ready
assigned to @nik and unassigned @hansegucker
Why not add
object__isnull=Falseto the filter above instead?objectis a proxy field for a generic foreign key and therefore can not be queried directly.resolved all threads
mentioned in commit
6f9b6ece9e