nextcloud / nextcloud/calendar
Can't search calendar by username
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 332
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 137
Description
Steps to reproduce
1.Choose to search by email address, users, and contacts
2.
3.
Expected behavior
Searches by username and email
Actual behaviour
Search is performed by email only, username@domain.com
Calendar app version
3.4.0
CalDAV-clients used
No response
Browser
Google Chrome 102.0.5005.61
Client operating system
Arch Linux
Server operating system
Oracle 8
Web server
Nginx
Database engine version
MariaDB
PHP engine version
PHP 7.4
Nextcloud version
24.0.2
Updated from an older installed version or fresh install
Fresh install
List of activated apps
Enabled:
- accessibility: 1.10.0
- activity: 2.16.0
- calendar: 3.4.0
- circles: 24.0.0
- cloud_federation_api: 1.7.0
- comments: 1.14.0
- contactsinteraction: 1.5.0
- dav: 1.22.0
- deck: 1.7.1
- event_update_notification: 1.5.0
- federatedfilesharing: 1.14.0
- federation: 1.14.0
- files: 1.19.0
- files_rightclick: 1.3.0
- files_sharing: 1.16.2
- files_trashbin: 1.14.0
- files_versions: 1.17.0
- firstrunwizard: 2.13.0
- ldap_contacts_backend: 1.2.0
- logreader: 2.9.0
- lookup_server_connector: 1.12.0
- nextcloud_announcements: 1.13.0
- notes: 4.3.1
- notifications: 2.12.0
- oauth2: 1.12.0
- password_policy: 1.14.0
- privacy: 1.8.0
- provisioning_api: 1.14.0
- recommendations: 1.3.0
- richdocuments: 6.1.0
- richdocumentscode: 21.11.402
- serverinfo: 1.14.0
- settings: 1.6.0
- sharebymail: 1.14.0
- spreed: 14.0.2
- support: 1.7.0
- survey_client: 1.12.0
- systemtags: 1.14.0
- text: 3.5.1
- theming: 1.15.0
- twofactor_backupcodes: 1.13.0
- updatenotification: 1.14.0
- user_ldap: 1.14.1
- user_status: 1.4.0
- viewer: 1.8.0
- weather_status: 1.4.0
- workflowengine: 2.6.0
Nextcloud configuration
{
"system": {
"instanceid": "***REMOVED SENSITIVE VALUE***",
"passwordsalt": "***REMOVED SENSITIVE VALUE***",
"secret": "***REMOVED SENSITIVE VALUE***",
"trusted_domains": [
"x.x.x.x",
"cloud.domain"
],
"datadirectory": "***REMOVED SENSITIVE VALUE***",
"dbtype": "mysql",
"version": "24.0.2.1",
"overwrite.cli.url": "https:\/\/cloud.domain",
"dbname": "***REMOVED SENSITIVE VALUE***",
"dbhost": "***REMOVED SENSITIVE VALUE***",
"dbport": "",
"dbtableprefix": "oc_",
"mysql.utf8mb4": true,
"memcache.local": "\\OC\\Memcache\\APCu",
"memcache.distributed": "\\OC\\Memcache\\Redis",
"redis": {
"host": "***REMOVED SENSITIVE VALUE***",
"port": 6379
},
"memcache.locking": "\\OC\\Memcache\\Redis",
"dbuser": "***REMOVED SENSITIVE VALUE***",
"dbpassword": "***REMOVED SENSITIVE VALUE***",
"installed": true,
"app_install_overwrite": [
"ldapcontacts",
"ldap_contacts_backend"
],
"maintenance": false,
"updater.secret": "***REMOVED SENSITIVE VALUE***",
"theme": "",
"loglevel": 2,
"ldapProviderFactory": "OCA\\User_LDAP\\LDAPProviderFactory"
}
}
Web server error log
No response
Log file
No response
Browser log
No response
Additional info
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named in the report. Start by reproducing the issue in the Calendar app with a username and email search on the listed versions, then trace the search entry point and add coverage showing that username and email both work; done means username searches return the expected users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, search
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100