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

Align lock and postprocessing info with sharing indicators #10538

Closed
12 tasks
kulmann opened this issue Mar 4, 2024 · 0 comments · Fixed by #10544
Closed
12 tasks

Align lock and postprocessing info with sharing indicators #10538

kulmann opened this issue Mar 4, 2024 · 0 comments · Fixed by #10544
Assignees
Labels
Type:Story User Story

Comments

@kulmann
Copy link
Member

kulmann commented Mar 4, 2024

Description

User Stories

  • As a user, I want to see important status information at a glance so that I immediately know which status a file/folder has.

Value

Make status info more prominent.

Acceptance Criteria

  • Rename the Shares column in the file list to Status
  • Move lock and postprocessing info into the Status column (= share indicators are now status indicators)
  • Remove the badge from ResourceIcon and preview image
  • Tiles view: try to fit the status indicators in between the file name and the context menu button (might need to increase the base tile size a bit in the theme)

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type:Story User Story
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants