nextcloud / nextcloud/files_retention

User interface tweaks

Open
#715 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage 1. to develop enhancement good first issue
Dominant language
JavaScript
Stars
42
Forks
24
Avg merge
2d 19h
Merged PRs (30d)
42

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

UI Tweaks as discussed in the design call

  • Heading --> Automatic file deletion (File retention)
  • Tags updated only on page reload
  • If no tags: Empty content with link that opens the tag creation section in the basic settings
  • Retention time label should be left aligned like other labels
  • Width of fields
    • First column wider by 50% more
    • Time units field can be narrower
    • Last column can be narrower
  • "Retention time" --> "Delete after"
  • "Time units"
    • Select components with 30 days, 90 days, 3 years, 7 years, custom?
    • Clicking on anything replaces the select with the time units+days/month/year components
  • Maybe create a component for selecting time + time unit

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files, tests, or entry points are named in the issue. Start by locating the UI for file retention settings and compare it with each unchecked item; clarify the unresolved component and select behavior before starting. Done means the agreed heading, labels, tag handling, field widths, and retention controls match the design call.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.