owned this note
owned this note
Published
Linked with GitHub
# Open Zaak, open issues, developer perspective
Issuelist: https://github.com/open-zaak/open-zaak/issues
Open Zaak / Open Notificaties & everything else
Next: page 4 of issues.
## high
* https://github.com/open-zaak/open-zaak/issues/869 - has impact on deployed containers -> limit impact by doing it asap, less than a week
* https://github.com/open-zaak/open-zaak/issues/863 - less than a day, WIP
* ~~https://github.com/open-zaak/open-zaak/issues/820 violates behaviour of standard, 1 week~~
* https://github.com/open-zaak/open-zaak/issues/795 less than a week, violates behaviour of standard
* https://github.com/open-zaak/open-zaak/issues/775 1 week? (investigate/reproduce)
* https://github.com/open-zaak/open-zaak/issues/772 used for the api-test.nl badge
* https://github.com/open-zaak/open-zaak/issues/726 day of work, PR is available
* https://github.com/open-zaak/open-zaak/issues/695 inconsistent and frustrating behaviour, likely leading to misconfigured case types. less than a week
* https://github.com/open-zaak/open-zaak/issues/684 dev experience, FB benefits a lot from this, about a week dev time
* https://github.com/open-zaak/open-zaak/issues/669 cut down user error, fill gaps in documentation, potential for fully automated install/configuration. 1 week
* https://github.com/open-zaak/open-zaak/issues/668 see #669, 1 day
## medium
* https://github.com/open-zaak/open-zaak/issues/871 - not needed for dev advancement, community value & dev-ops value is higher
* https://github.com/open-zaak/open-zaak/issues/830 ^ see above, less than a day. essentially plans/reserves time for devops engineers when an important release becomes available
* https://github.com/open-zaak/open-zaak/issues/870 (less than a day), doesn't generate community support noise, allows people building apps on top of OZ effectively (dev-experience)
* https://github.com/open-zaak/open-zaak/issues/862 - there will be people for who the current naming is exclusive
* https://github.com/open-zaak/open-zaak/issues/854 - ~1 day of work, devops-experience
* https://github.com/open-zaak/open-zaak/issues/851 - dev-experience, 2 days worth of work
* https://github.com/open-zaak/open-zaak/issues/850 - dev-experience, 1 day
* https://github.com/open-zaak/open-zaak/issues/805 would be resolved by #810, #855, breaks expectations
* https://github.com/open-zaak/open-zaak/issues/796 less than a day, reduce dev/community support noise
* https://github.com/open-zaak/open-zaak/issues/635 see #796 above
* https://github.com/open-zaak/open-zaak/issues/761 size depends on implementation choice -> Sentry highly recommended
* https://github.com/open-zaak/open-zaak/issues/693 less than a week, FB does a lot in bulk
* https://github.com/open-zaak/open-zaak/issues/687 dev-experience, 1 day
* https://github.com/open-zaak/open-zaak/issues/683 1 day
* https://github.com/open-zaak/open-zaak/issues/644 1 day, allows strict network control, security improvement
* https://github.com/open-zaak/open-zaak/issues/636 is confusing when checking data on the spot in POCs with client development for example. 1 day
* https://github.com/open-zaak/open-zaak/issues/601 documenting it takes almost same amount of work as fixing, undocumented workaround available. 1 day
## low
* https://github.com/open-zaak/open-zaak/issues/855 - standalone admin interface would cost about 2~3 months, would reduce Open Zaak complexity in the admin customization. effort moves to standalone app with own release cycle, would solve #805 and #699
* https://github.com/open-zaak/open-zaak/issues/810 see #855
* https://github.com/open-zaak/open-zaak/issues/699 see #855
* https://github.com/open-zaak/open-zaak/issues/847 (fix link to KP-API), 1 day of work
* https://github.com/open-zaak/open-zaak/issues/829
* https://github.com/open-zaak/open-zaak/issues/809 less than a week
* https://github.com/open-zaak/open-zaak/issues/745 less than a week
* https://github.com/open-zaak/open-zaak/issues/729 available feature-flag based workaround
* https://github.com/open-zaak/open-zaak/issues/709 no perf problem atm
* https://github.com/open-zaak/open-zaak/issues/705
* https://github.com/open-zaak/open-zaak/issues/682 would rather see a dedicated application
* https://github.com/open-zaak/open-zaak/issues/661 rather invest in SSO/OpenID Connect
* https://github.com/open-zaak/open-zaak/issues/647 implementation detail
* https://github.com/open-zaak/open-zaak/issues/646 documentation issue
* https://github.com/open-zaak/open-zaak/issues/643
* https://github.com/open-zaak/open-zaak/issues/639 failed notifications end up in logging and don't prevent using Open Zaak
* https://github.com/open-zaak/open-zaak/issues/621 similar as #639, implement envvar to disable notifications
* https://github.com/open-zaak/open-zaak/issues/631 less than a week, ratio effort vs benefits is unfavourable
*
## out of scope
* https://github.com/open-zaak/open-zaak/issues/866
* https://github.com/open-zaak/open-zaak/issues/860
* https://github.com/open-zaak/open-zaak/issues/835 (already being worked on)
* https://github.com/open-zaak/open-zaak/issues/833
* https://github.com/open-zaak/open-zaak/issues/787
* https://github.com/open-zaak/open-zaak/issues/781
* https://github.com/open-zaak/open-zaak/issues/774
* https://github.com/open-zaak/open-zaak/issues/759
* https://github.com/open-zaak/open-zaak/issues/748 (product steering group should follow this up better?)
* https://github.com/open-zaak/open-zaak/issues/744 needs follow up, what is the user trying to do?
* https://github.com/open-zaak/open-zaak/issues/707 standalone tooling
* https://github.com/open-zaak/open-zaak/issues/706 bring it up in upstream standard
* https://github.com/open-zaak/open-zaak/issues/688
* https://github.com/open-zaak/open-zaak/issues/680
* https://github.com/open-zaak/open-zaak/issues/679
* https://github.com/open-zaak/open-zaak/issues/678
* https://github.com/open-zaak/open-zaak/issues/673
* https://github.com/open-zaak/open-zaak/issues/659
* https://github.com/open-zaak/open-zaak/issues/642
* https://github.com/open-zaak/open-zaak/issues/620
* https://github.com/open-zaak/open-zaak/issues/619
* https://github.com/open-zaak/open-zaak/issues/618
* https://github.com/open-zaak/open-zaak/issues/617
* https://github.com/open-zaak/open-zaak/issues/607
* https://github.com/open-zaak/open-zaak/issues/602
* https://github.com/open-zaak/open-zaak/issues/601
*