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

Email subfolders #927

Open
armhub opened this issue Dec 11, 2018 · 9 comments
Open

Email subfolders #927

armhub opened this issue Dec 11, 2018 · 9 comments

Comments

@armhub
Copy link
Contributor

@armhub armhub commented Dec 11, 2018

No description provided.

@armhub armhub added this to the Roadmap milestone Dec 11, 2018
@charlag charlag added this to Planned in Roadmap Project Jan 30, 2019
@portstrom
Copy link

@portstrom portstrom commented Sep 10, 2019

I believe that having a hierarchy of subfolders will make things significantly more complicated, both in terms of implementation and in terms of UX. I would recommend canceling this feature and instead implementing tags (#318), which are both simpler and more versatile. I would go as far as to recommend removing the folders feature altogether to replace it with tags.

@4jNsY6fCVqZv
Copy link

@4jNsY6fCVqZv 4jNsY6fCVqZv commented Oct 6, 2019

@portstrom Exciting idea with the tags, I like well!
@armhub And somehow I am curious to understand why there is no possibility for subfolders yet. That must have been a conscious decision on your part, right? Cause folders are so standard classic feature, aren't they?
I also think that with tags and a good search it becomes easier to think/organize than in folders, because tags can express more connections than a single folder.

@armhub
Copy link
Contributor Author

@armhub armhub commented Oct 7, 2019

As @portstrom already pointed out, the UI would be much more complex with subfolders, therefore we decided to just allow a set of custom folders which is shown below the system folders.
But when implementing email import (#630) we will have to rethink this because imported mailboxes may have subfolders and we will have to decide how to handle them in Tutanota.

@4jNsY6fCVqZv
Copy link

@4jNsY6fCVqZv 4jNsY6fCVqZv commented Oct 8, 2019

Thank you for your explanation! Do you already have any ideas how such a mixed design could look like? Or does that mean that the tag solution can't be focused?

@MystifyBFC

This comment was marked as off-topic.

@Feuizl
Copy link

@Feuizl Feuizl commented Apr 23, 2020

Tags could work well for me although I would prefer folders.

Just use tags for Friends/VIP, Unread, etc.

@reenko
Copy link

@reenko reenko commented May 12, 2020

In the current version, I can't order my custom folders by myself, getSortedCustomFolders sorting by names. Will it be possible for sub-folders or tags? Should I create a separate request?

@charlag
Copy link
Contributor

@charlag charlag commented May 14, 2020

@reenko we don't accept feature requests here, please use support or Reddit

@akg83
Copy link

@akg83 akg83 commented Dec 30, 2020

@portstrom As a developer my self, I do not understand what is so complicated in adding one additional level to the top level folders?

@armhub I guess that multiple levels of sub folders will be unnecessary complicated or irritating to the UI, but adding at least one additional level to the top level custom folders is IMHO very basic, especially when Tutanota is offering people email aliases that might be used for multiple (and many) different usages. if it was possible to add to the top level custom folders just one more level of child sub-folders that could be perfect, and I am not the only person who think like that.

Adding tags is cute, but too many tags are a terrible idea for a practical UI, tags will be a great addition to assist with searching (e.g. searching by tags), but not as a replacement for the parent -> child custom folder feature.

Do what you think is right, but discarding such an essential (and pretty standard) feature will be pity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Roadmap Project
  
Planned
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
8 participants