You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the Bug:
The filters in the attachment table don't work. This makes it hard for users to find the right file when dealing with 20+ attachments.
Probability (how likely the bug is to happen, scored from 1-5): 5
(For example, probability of 5 is something like "it happens to all users every time they log in."
Probability of 1 "only happens to certain users when a really specific and unlikely path is followed.")
Effect (how bad the bug is when it does happen, scored from 1-5):2
(For example, effect of 5 is "the entire app crashes and makes it unusable for all users" or "the bug causes the wrong data to be saved, with critical information (e.g. payment) being affected."
Effect of 1 is "It makes some styling look a little bit weird.")
Steps to reproduce the behaviour:
Filter attachments on either view or edit attachments for a project
Screenshots:
Additional information:
OS: [e.g. iOS]
Browser: [e.g. chrome, safari]
Version: [e.g. 22]
Additional context
The text was updated successfully, but these errors were encountered:
pbastia
changed the title
Bug: Filters don't work on the project attachment page (both view and edit)
CIF: Bug: Filters don't work on the project attachment page (both view and edit)
Jul 11, 2024
@patriciarussellCAS@dleard Having a look at the code, this one will be a tricky one. It will require rewiring quite a few pages and components to accept search parameters to let them pass through our attachments table. The side effects are also hard to gauge.
We could also try and implement basic filtering on the client side (especially since pagination doesn't work 🥴 )
I stand by my estimate of about 5 days FTE of work.
Describe the Bug:
The filters in the attachment table don't work. This makes it hard for users to find the right file when dealing with 20+ attachments.
Probability (how likely the bug is to happen, scored from 1-5): 5
(For example, probability of 5 is something like "it happens to all users every time they log in."
Probability of 1 "only happens to certain users when a really specific and unlikely path is followed.")
Effect (how bad the bug is when it does happen, scored from 1-5):2
(For example, effect of 5 is "the entire app crashes and makes it unusable for all users" or "the bug causes the wrong data to be saved, with critical information (e.g. payment) being affected."
Effect of 1 is "It makes some styling look a little bit weird.")
Steps to reproduce the behaviour:
Filter attachments on either view or edit attachments for a project
Screenshots:
Additional information:
The text was updated successfully, but these errors were encountered: