-
Notifications
You must be signed in to change notification settings - Fork 260
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
Mail gap analysis issues #5478
Comments
FYI @nimisha-vijay in case there are other ones. :) This is for easier tracking them in a bunch. |
@ChristophWurst @AndyScherzinger FYI this one was missing: #1626 – also a bit more advanced. |
Could we just tag all those tickets linked here with feature parity ? Feature parity is the gap we have to close to other clients. |
@ChristophWurst DONE 👍 |
Then we possibly can delete this ticket. We have them grouped by the tag and they are also in our backlog. Do we need the grouping for anything else @jancborchardt? |
Sounds good to me and I agree especially since there might be new gaps to be foun din the future, so it is rathe ra category via a label than a meta/overview issue that never gets closed due to constant new findings over time... |
Closing this then. :) |
The text was updated successfully, but these errors were encountered: