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

Choose link/share expiration based on time span instead of calendar #11533

Open
12 tasks
kulmann opened this issue Sep 6, 2024 · 2 comments
Open
12 tasks

Choose link/share expiration based on time span instead of calendar #11533

kulmann opened this issue Sep 6, 2024 · 2 comments
Labels
Priority:p4-low Low priority Type:Story User Story

Comments

@kulmann
Copy link
Member

kulmann commented Sep 6, 2024

Description

Some users prefer selecting the expiry date of a link or share based on a validity duration (e.g. 30 days) instead of finding the appropriate date in the calendar.

User Stories

  • As a user, I want to define an expiry of a link or share by a number of days so that I don't have to calculate in my head a date from the current date + a certain amount of days or weeks.

Value

Fast expiry input without cognitive load.

Acceptance Criteria

  • user can decide in preferences whether they want to enter expiry dates by number of days or by calendar input
  • any place where an expiration date can be picked now adheres to this preference

Definition of ready

  • Everybody needs to understand the value written in the user story
  • Acceptance criteria have to be defined
  • All dependencies of the user story need to be identified
  • Feature should be seen from an end user perspective
  • Story has to be estimated
  • Story points need to be less than 20

Definition of done

  • Functional requirements
    • Functionality described in the user story works
    • Acceptance criteria are fulfilled
  • Quality
    • Code review happened
    • CI is green (that includes new and existing automated tests)
    • Critical code received unit tests by the developer
  • Non-functional requirements
    • No sonar cloud issues
@kulmann kulmann added the Type:Story User Story label Sep 6, 2024
@kulmann
Copy link
Member Author

kulmann commented Sep 6, 2024

cc @tbsbdr @dj4oC

@kulmann kulmann moved this from Qualification to Backlog in Infinite Scale Team Board Sep 6, 2024
@tbsbdr tbsbdr added the Priority:p4-low Low priority label Sep 6, 2024
@AlexAndBear
Copy link
Contributor

AlexAndBear commented Sep 6, 2024

Thanks for opening the ticket, even if we want to add this setting. For the current date picker itself, I'd still like to show the relative date: this is tackled by #11534

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority:p4-low Low priority Type:Story User Story
Projects
Status: Backlog
Development

No branches or pull requests

3 participants