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

make editing of fiel attributes easier #2209

Open
14 tasks
only1chunts opened this issue Feb 18, 2025 · 1 comment
Open
14 tasks

make editing of fiel attributes easier #2209

only1chunts opened this issue Feb 18, 2025 · 1 comment

Comments

@only1chunts
Copy link
Member

User story

As a curator
I want the edit file attibutes feature to be as user friendly as the create new file attributes feature
So that I can benefit

Acceptance criteria

Given there is a file with an attribute already in GigaDB e.g. https://staging.gigadb.org/adminFile/update/id/548444
When I need to edit a file attribute
Then the fields are displayed better than this:

Image

Additional Info

the create new file attributes was fixed by @luistoptal previously, but the edit option still has very small boxes particularly for the value, maybe #2108 will aleviate the issue?

Product Backlog Item Ready Checklist

  • Business value is clearly articulated
  • Item is understood enough by the IT team so it can make an informed decision as to whether it can complete this item
  • Dependencies are identified and no external dependencies would block this item from being completed
  • At the time of the scheduled sprint, the IT team has the appropriate composition to complete this item
  • This item is estimated and small enough to comfortably be completed in one sprint
  • Acceptance criteria are clear and testable
  • Performance criteria, if any, are defined and testable
  • The Scrum team understands how to demonstrate this item at the sprint review

Product Backlog Item Done Checklist

  • Item(s) in increment pass all Acceptance Criteria
  • Code is refactored to best practices and coding standards
  • Documentation is updated as needed
  • Data security has not been compromised (with particular reference to the personal information we hold in GigaDB)
  • No deviation from the team technology stack and software architecture has been introduced
  • The product is in a releasable state (i.e. the increment has not broken anything)
@luistoptal
Copy link
Collaborator

Hi @only1chunts this is fixed by an already existing PR #2082

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

2 participants