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

View count of entries in each Group #3963

Closed
Gravip opened this issue Dec 1, 2019 · 9 comments · Fixed by #8435
Closed

View count of entries in each Group #3963

Gravip opened this issue Dec 1, 2019 · 9 comments · Fixed by #8435
Assignees
Milestone

Comments

@Gravip
Copy link

Gravip commented Dec 1, 2019

It can be near Groups. It isn't unneeded future, for example I need to understand how many entries are not in my second base on another device witch I don't want sync via cloud.

@droidmonkey droidmonkey changed the title Future: View count of entries in each Group View count of entries in each Group Dec 1, 2019
@droidmonkey droidmonkey added this to the v2.7.0 milestone Aug 3, 2020
@droidmonkey droidmonkey modified the milestones: v2.7.0, v2.7.1 Mar 21, 2022
@droidmonkey
Copy link
Member

Need to add this to the status bar since we are showing that now.

@phoerious phoerious modified the milestones: v2.7.1, v2.7.2 Apr 12, 2022
@tehmasterer
Copy link

Is this happening? Seems like such a basic feature...

@droidmonkey
Copy link
Member

I just implemented it, will be in an upcoming PR. We have included thousands of other basic features can't do everything unfortunately.

@tehmasterer
Copy link

Appreciate it. I didn't mean to sound ungrateful, just genuinely surprised no one got to it until now.

droidmonkey added a commit that referenced this issue Sep 1, 2022
droidmonkey added a commit that referenced this issue Sep 1, 2022
droidmonkey added a commit that referenced this issue Sep 3, 2022
droidmonkey added a commit that referenced this issue Sep 3, 2022
droidmonkey added a commit that referenced this issue Sep 5, 2022
droidmonkey added a commit that referenced this issue Sep 5, 2022
droidmonkey added a commit that referenced this issue Sep 5, 2022
droidmonkey added a commit that referenced this issue Sep 5, 2022
droidmonkey added a commit that referenced this issue Sep 5, 2022
droidmonkey added a commit that referenced this issue Sep 7, 2022
droidmonkey added a commit that referenced this issue Sep 7, 2022
droidmonkey added a commit that referenced this issue Sep 7, 2022
droidmonkey added a commit that referenced this issue Sep 7, 2022
droidmonkey added a commit that referenced this issue Sep 7, 2022
droidmonkey added a commit that referenced this issue Sep 7, 2022
droidmonkey added a commit that referenced this issue Sep 8, 2022
pull bot pushed a commit to annihilatorrrr/keepassxc that referenced this issue Sep 8, 2022
pull bot pushed a commit to tigerwill90/keepassxc that referenced this issue Sep 8, 2022
droidmonkey added a commit that referenced this issue Sep 11, 2022
droidmonkey added a commit that referenced this issue Sep 22, 2022
@macsunmood
Copy link

Sorry, how is this implemented in ver. 2.7.1 ?

@jamilraichouni
Copy link

Not important but worth mentioning:
When using the macos GUI in English it states 2 Entry(s) for instance. But it must be x Entries if x > 1.
So in the case of the english word Entry you cannot cover singular and plural by appending the suffix (s). That works for User -> User(s) and many other english words but not in the given case or for 1 Baby and x Babies etc.

@phoerious
Copy link
Member

phoerious commented Oct 26, 2022

Entry(s) is the correct source string. Providing the proper singular and plural forms is the job of the English translation, which is managed on Transifex.

@jamilraichouni
Copy link

Entry(s) is the correct source string. Providing the proper singular and plural forms is the job of the English translation, which is managed on Transifex.

Well then this will better be reported (I suggest by @droidmonkey who worked on that here #8435 ) to the developers of Transifex so that they can fix it, right?

@droidmonkey
Copy link
Member

I already fixed it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants