github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-06 03:27:53 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[PR #1200] [MERGED] feat: show user export status in settings #4788

New Issue
Closed
opened 2026-04-16 13:16:07 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-16 13:16:07 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/go-vikunja/vikunja/pull/1200
Author: @kolaente
Created: 7/30/2025
Status: ✅ Merged
Merged: 7/30/2025
Merged by: @kolaente

Base: main ← Head: codex/plan-user-data-exports-interface

📝 Commits (8)

📊 Changes

13 files changed (+181 additions, -5 deletions)

View changed files

📝 .gitignore (+0 -1)
📝 frontend/src/i18n/lang/en.json (+3 -1)
📝 frontend/src/services/dataExport.ts (+4 -0)
📝 frontend/src/views/user/DataExportDownload.vue (+8 -1)
📝 frontend/src/views/user/settings/DataExport.vue (+75 -2)
📝 pkg/db/fixtures/users.yml (+1 -0)
📝 pkg/models/label_test.go (+2 -0)
📝 pkg/models/project_users_test.go (+1 -0)
📝 pkg/models/task_collection_test.go (+1 -0)
📝 pkg/models/user_project_test.go (+1 -0)
📝 pkg/routes/api/v1/user_export.go (+43 -0)
📝 pkg/routes/routes.go (+1 -0)
➕ pkg/webtests/user_export_status_test.go (+41 -0)

📄 Description

This PR adds functionality to show an existing user data export in the user settings.

Things done:

  • add API endpoint GET /user/export
  • display export metadata in DataExport settings page
  • link back to request page from download view
  • add English translations
  • add test for export status endpoint

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/go-vikunja/vikunja/pull/1200 **Author:** [@kolaente](https://github.com/kolaente) **Created:** 7/30/2025 **Status:** ✅ Merged **Merged:** 7/30/2025 **Merged by:** [@kolaente](https://github.com/kolaente) **Base:** `main` ← **Head:** `codex/plan-user-data-exports-interface` --- ### 📝 Commits (8) - [`16f3d4c`](https://github.com/go-vikunja/vikunja/commit/16f3d4ca7e58f7e148141a39de5d2af7b92d39c5) feat: list current user data export - [`d98a17b`](https://github.com/go-vikunja/vikunja/commit/d98a17b76c2174923fd699788f38159614766c6e) fix lint - [`d08d87d`](https://github.com/go-vikunja/vikunja/commit/d08d87ddef51a947067ca4ba80095d0d737114e7) make things work - [`2d039f5`](https://github.com/go-vikunja/vikunja/commit/2d039f5852f8456e9151e2d009f4703cda2606f0) make things prettier - [`b2455dc`](https://github.com/go-vikunja/vikunja/commit/b2455dcddaff1a9c480e07d9066d8451fd46ba78) remove plan - [`4639cd6`](https://github.com/go-vikunja/vikunja/commit/4639cd6f96d7ec8f4d0e0693f1fcf7f5b795f957) fix test - [`565d1c4`](https://github.com/go-vikunja/vikunja/commit/565d1c4b564d86cb0c86d4755c892405a919d8b7) actually fix test - [`6cca577`](https://github.com/go-vikunja/vikunja/commit/6cca5779d983ee4f053c8f88d6fa8be30a72b099) fix test fxturs ### 📊 Changes **13 files changed** (+181 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `.gitignore` (+0 -1) 📝 `frontend/src/i18n/lang/en.json` (+3 -1) 📝 `frontend/src/services/dataExport.ts` (+4 -0) 📝 `frontend/src/views/user/DataExportDownload.vue` (+8 -1) 📝 `frontend/src/views/user/settings/DataExport.vue` (+75 -2) 📝 `pkg/db/fixtures/users.yml` (+1 -0) 📝 `pkg/models/label_test.go` (+2 -0) 📝 `pkg/models/project_users_test.go` (+1 -0) 📝 `pkg/models/task_collection_test.go` (+1 -0) 📝 `pkg/models/user_project_test.go` (+1 -0) 📝 `pkg/routes/api/v1/user_export.go` (+43 -0) 📝 `pkg/routes/routes.go` (+1 -0) ➕ `pkg/webtests/user_export_status_test.go` (+41 -0) </details> ### 📄 Description This PR adds functionality to show an existing user data export in the user settings. Things done: - add API endpoint `GET /user/export` - display export metadata in DataExport settings page - link back to request page from download view - add English translations - add test for export status endpoint --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-16 13:16:07 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#4788
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?