Bug Bash Fundamentals
What is a bug bash?
It’s a collaborative event where the whole team, no matter what their role is, comes together to try to “break” the application in creative ways ahead of a release. The goal is to find as many bugs as possible in a short period of time, and since every person in the team will have their own unique perspective and use the application in different ways, there are better chances of uncovering issues, defining how severe they are and if needed fixing them ahead of the release. It’s also a great opportunity for people to spend some time familiarizing themselves with the application and putting themselves in the shoes of one of our users. And last but not least, breaking things can actually be fun! By doing bug bashes often, we’re cultivating a blame-free culture where we take bugs as a chance to bond as a team, learn and improve.
How do I participate?
If you’re willing to collaborate with this bug bash, please write your name down in the Participants section. If possible add details about what language(s) you’re using when testing the app, as well as which user role(s) you’re logging in as. This will help us know if there are any languages or roles not currently being covered by anyone.
Read through the scope of what we’re testing in the Scope section. The scope will usually be defined based on what kind of changes we are pushing out on the upcoming release and it’s a guidance on which are the main things to keep an eye on. That being said, if you do find any bugs that are unrelated to the scope, feel free to report them anyway.
If the bug bash is done synchronously, there’ll be a meeting where we all come together and test at the same time with a time box. If it’s done asynchronously, we’ll aim to have the session open for enough time that people in different timezones are able to participate. In that case, feel free to participate whenever you can and have the time and to time box depending on what your schedule looks like. Everything helps, so even if you only have limited time to test, you might discover something that nobody else has found before. Information on the timing of the meeting or asynchronous session can be found in the Session details section
What do I do if I find a bug?
First off, congratulations on finding it! To report the bug, head over to the Bugs section and add a new row in the table. The row should include your name and a brief description of the bug, on the Details field please add as much information as possible. Please provide reproduction steps and expected/actual behavior, and if you have the time, screenshots or video recordings of what you encountered will be extremely helpful. You don’t need to fill out the Pre-existing, Priority or Blocker fields as those will be filled out once the session is over.
If you spot a bug and you see someone else has already reported it and it’s on the table, you can go ahead and just add your name to the “Also seen by” column to mark that the bug is encountered frequently, without having to write down all the details again.
What happens after the bug bash?
Once the bug bash session is over, the team will go over the list of bugs that were found and prioritize them. For each issue, we’ll try to answer these three questions:
Was this bug caused by the change we’re aiming to push out on this release, or does it currently exist in production?
How severe and how frequent is this bug, or in other words, what’s the priority for fixing it?
Should this bug block the upcoming release?
No matter the result, if the issue found is something we’d like to fix eventually, we’ll create the corresponding ticket in Jira and add it to the Backlog. If we come to the conclusion that one or more bugs are actually blocking the upcoming release, we’ll add those tickets to the current sprint and give them the highest priority. If no bugs are found that are blocking, we’ll proceed with the release process as normal and work on the reported issues in future sprints depending on their priority.
Participants
Name | Language(s) | User role(s) |
|---|---|---|
E.g.: Anto Sgarlatta | E.g.: Spanish, English | E.g.: Farm Owner, Farm Worker |
English | Farm Owner | |
English, Punjabi | Farm Manager, Farm Worker | |
English, Japanese | Farm Owner | |
Portuguese, English | Farm Manager | |
English, French | Farm Owner and Farm Worker | |
Spanish | Farm manager | |
Scope
This bug bash will concentrate on testing the features introduced in the patch which introduces powerful new functionality, enabling users to create and manage animals within LiteFarm. With this update, users can efficiently plan and document animal management processes, ensuring proper execution by the assigned staff. If you would like to learn more about the specific changes, find additional details here: https://lite-farm.atlassian.net/projects/LF/versions/10019/tab/release-report-all-issues
Purpose of the Patch:
The update aims to empower users with the ability to create and manage animals within LiteFarm. To ensure this functionality is working as expected, thorough testing will be required across all related features.
Key Areas to Test:
Animal Creation:
Creating a single animal.
Creating a batch of animals.
Animal Management:
Editing animal details (e.g., name, breed, health status, etc.).
Deleting animals (individual and batch).
Data Validation and Interactions:
Ensure accurate data entry and validation across forms.
Verify that updates are correctly reflected in the UI
Usability and Edge Cases:
Verify the user interface and experience during the creation, editing, and deletion processes.
Test edge cases (e.g., invalid input, large batch sizes, and boundary conditions).
Performance and Load:
Assess system performance when managing large numbers of animals.
Ensure batch operations execute efficiently.
Deliverables:
Confirm that all features related to animal management function as intended.
Identify and document any bugs, inconsistencies, or areas of improvement.
Provide feedback on usability and overall experience.
Thank you for your attention to detail during this critical testing phase! Your insights will be invaluable in ensuring a smooth rollout of these new features.
User Stories
As a (potential) LiteFarm user of any role:
Animal Management Guidelines
Viewing and Adding Animals
Viewing Animals:
Ensure that accessing the Animals page displays all previously created animals.
Verify that the option to create new animals is visible, except for Farm Worker accounts (who should not see the create option).
Adding New Animals:
Starting the Creation Process:
Confirm that clicking the “+” button in the bottom-left corner of the app initiates the process to add new animals to the farm.
Required Fields Validation:
Ensure that the creation process cannot be completed without filling in all required fields.
Adding Multiple Animal Types:
Verify that users can create two or more animal types during the same process by clicking the “+ Add More Animals” button.
Individual and Batch Creation:
Ensure users can create both individual animal profiles and animal batches seamlessly.
Adding Custom Animal Types and Breeds:
Confirm that users can add custom animal types and custom breeds by typing a name that does not already exist on their farm.
Preventing Duplicate Custom Entries:
Verify that users cannot create a custom animal type or custom breed if it already exists on their farm.
Removing Animals During Creation:
Ensure users can remove animals during the creation process by clicking the “Remove” button on the corresponding animal card.
Handling Page Reload or Cancel:
Check that reloading the page or clicking the “Cancel” button triggers an informative pop-up message warning users that their progress will be discarded.
Animal Movement Task
Task Display:
Confirm that the Tasks page displays all tasks related to the user’s farm.
Creating a Movement Task:
Verify that clicking the “+” button allows the user to select “Movement Task.”
Ensure that users can select multiple animals or batches during the creation process.
Location Selection:
Confirm that during the creation of an Animal Movement task, users can choose from the following locations:
Barn, Field, Garden, Greenhouse Area, Natural Area, Surface Water, and Buffer Zone.
Ensure that the following locations cannot be selected:
Ceremonial Area, Residence, Watercourse, Gate, Fence, Farm Boundary, and Water Valve.
Custom Task Type Creation
Creating a New Custom Task Type:
Verify that users can successfully create a new custom task type without issues.Duplicate Prevention:
Ensure that the system prevents the creation of duplicate custom task types (i.e., task types with the same name as an existing one).Deleting a Custom Task Type:
Confirm that users can delete a custom task type after it has been created.
Creating a Custom Task
Animal-Related Tasks:
Verify that users can create custom tasks specifically related to animals (e.g., cleaning, feeding, animal health check or movement tasks).General Tasks:
Ensure that users can create custom tasks that are not related to animals, allowing for flexibility in task creation.
Custom Task Management
Deleting Custom Task Types:
Confirm that users can delete a custom task type, ensuring it is removed from the system while maintaining the integrity of existing tasks.Completing or Abandoning Custom Tasks:
Verify that users can complete or abandon a custom task once it has been created.Modifying Tasks During Completion:
Ensure that users can make necessary changes to a custom task (e.g., updating due dates or assignees) while the task is still in progress.
Additional Considerations:
Test edge cases such as invalid input (e.g., empty task type names) and boundary conditions (e.g., maximum character limits for names).
Assess the usability and performance when managing a large number of custom task types or tasks.
Confirm that permissions for creating and managing custom tasks align with user roles (e.g., Farm Worker restrictions).
Task Management Testing Guidelines
Completing Tasks:
Verify that users can successfully complete the Animal Movement Task and that it is marked as completed in the system.Post-Completion Restrictions:
Ensure that once the task is marked as completed, no further changes can be made to its details, and attempts to modify values are prevented.Editing Task Details:
Confirm that users can update the “Due Date” and “Assignee” for tasks that are still active (not completed).Farm Worker Permissions:
Task Creation Restriction: Verify that Farm Worker accounts cannot create an Animal Movement Task.
Task Completion Permission: Ensure that Farm Workers can complete Movement Tasks assigned to them.
Assignee Modification Restriction: Confirm that Farm Workers cannot change the assignee if the task is already assigned to someone else.
Task Deletion or Abandonment:
Ensure that users retain the ability to delete or abandon an Animal Movement Task as needed, provided it is not marked as completed.
Filters Functionality
Filter Accuracy:
Test various filter combinations to ensure they return the correct results.
KPI Animal Card Updates:
Confirm that KPI animal cards update accurately as new animals are added to the farm.
KPI Card Filtering:
Verify that clicking a KPI animal card correctly filters the results displayed in the animal table.
Account Permissions
FO/FM/EO Account Permissions:
Confirm that Farm Owner (FO), Farm Manager (FM), and Extension Officer (EO) accounts can:
Create movement tasks.
Manage animals, including creating, editing, and deleting profiles or batches.
Farm Worker Account Restrictions:
Ensure that Farm Worker accounts cannot:
Create movement tasks.
Delete or create new animals.
Farm Worker Access:
Verify that Farm Worker accounts can:
Access and view the Animals Inventory page.
Complete movement tasks assigned to them.
Movement Task Creation Process
Completing Tasks:
During Movement Task creation, verify that users can assign the task to themselves and mark it as completed.
Cancelling Task Creation:
Ensure that clicking the “Cancel” button displays a confirmation pop-up:
Clicking “No” allows users to continue the process.
Clicking “Yes” aborts the process and redirects users to the Tasks page.
Post-Creation Verification:
After creating a task, confirm that task details are accurate and visible in view-only mode on the Tasks page.
Ensure that notifications are triggered for assignees when tasks are created, completed, abandoned, or deleted.
Task Management:
Verify that users can delete or abandon tasks after they are created.
Confirm that navigating back and forth during the task creation flow retains previously entered information.
Finance Documentation
Ensure that upon completing or abandoning a movement task or a custom task, the labor expense is calculated correctly and reflected on the Finances page.
Support requests or feedback
Ensure that you are able to send the support request to a LiteFarm support team. ( We changed the position of that button, now you may find it in the top right corner of the app.)
Ensure that all the information is visible and translated correctly.
Ensure that you are not able to send it without filling all the required information
Adding Usability Suggestions
To ensure a user-friendly experience, we encourage testers to share their insights and feedback regarding usability improvements. You can submit your suggestions directly in the testing document under a dedicated section titled "Usability Suggestions."
Be specific about the feature or area of the application your suggestion pertains to.
Provide clear descriptions of your observations or proposed changes to help the team understand and address your feedback effectively.
Your input is invaluable in enhancing the LiteFarm experience!
Usability Suggestions:
Reporter | Description | Details | Have the same opinion? |
|---|---|---|---|
E.g.: Anto Sgarlatta | E.g.: The “+” add button is too large | E.g.: Repro steps
Expected Should navigate to the Google page to choose an account Actual Nothing happens Screenshots/videos | E.g. Joyce Sato-Reinhold |
Some way to pre-fill more of the animal creation data | Repro steps
Expected Either able to specify more/most fields on the previous screen, or some other mechanism Actual Must add details to each individual animal. Screenshots/videos | I have started some designs solving this particular issue, it’s a good feature to add in the future. Also I would think we would tackle the CSV animal upload before that, as I’d argue if you have 100 individuals animals to add, it’s not the right UI for that. | |
Sire & Dam, and Supplier should should be linked to animals and suppliers respectively | Repro steps
Expected It is a search/select field Actual Reconciling duplicates when we do this will be fun Screenshots/videos | Anto Sgarlatta the reason we went for a text field was to reduce complexity since sire/dam could be animals not in the farm (related to item below, but it’s possible the user wouldn’t want to track animals not in their farm) Duncan Brain my concerns about reconciling future data specifically with regards to expenses are helped by Loic Sans point that we should never ever try to convert these into expenses, the user may bypass our lack of linking and create the expense themselves while we develop that feature. Sire and dam can be converted in the future with less issues. | |
A third option to “Born here”, “Brought in” might be “Breed Lineage” or “Not on farm” | Repro steps
Expected It is linked to animals, and the animal does not have to exist on farm Actual No such option Screenshots/videos | ||
If I enter cost and supplier I expect an expense to be made. | Repro steps
Expected There is now an expense Actual No such expense Screenshots/videos | ?: Actually had the same opinion. Duncan Brain Just thinking we don’t want this data until we have thought though lineage and related expenses. (better to have less bad data than more data to fix in the future Duncan Brain my concerns about reconciling future data specifically with regards to expenses are helped by Loic Sans point that we should never ever try to convert these into expenses, the user may bypass our lack of linking and create the expense themselves while we develop that feature. Sire and dam can be converted in the future with less issues. | |
I expect profile options to be furthest top right corner | Repro steps
Expected This might be subjective but I thought profile normally in top right corner Actual Feedback message is there Screenshots/videos | Let’s monitor this and see if we get the same feedback. | |
A way to deselect/select all in mobile view in tasks | Repro steps
Expected A way to select all animals or deselect all animals Actual Not present
Screenshots/videos | Will look into this | |
Accidental click outside checkbox goes to details view and loses check progress | Repro steps
Expected Checkbox clicked or nothing happens Actual Redirected to animal details Screenshots/videos | Joyce Sato-Reinhold OMG YES I WAS JUST MAKING A VIDEO Anto Sgarlatta a better UX patern would be a way to get in/out of selection mode. Nested clickable areas are also really bad for accessibility https://gitnation.com/contents/nested-interactive-elements-an-nightmare-in-accessibility | |
System keyboard obscures “Set” (save) button on SexDetails popup (mobile, android) | Repro steps
Expected
Actual
Screenshots/videos   | ||
Once the user creates an animal it may be not quite clear where you will be redirected once you will click on the “Add more details to your animals” button | Repro steps
Expected Actually for me it was expected that I will be redirected to the animal detail page of the batch that I have just created. Actual I am redirected to the Animals inventory page. Screenshots/videos  | Joyce Sato-Reinhold I was thinking about this again when we watched Divya add new animals and the new entry popped up in the middle of the table and was therefore hard to locate. Was navigating to the inventory a placeholder before the details view was created? | |
No reason for abandoning options for animal tasks | Repro steps
Expected It would be nice if we could add expected reasons for animal tasks in the future Actual No options for animal tasks Screenshots/videos | ||
Support: Display ‘file’ instead of ‘image’ | Repro steps
Expected Given that the uploaded content can have various formats, the options displayed should be: Actual The options displayed are: Screenshots/videos  | ||
“Mobile” view extends to 1200px for all animal inventory-related views Mobile view has:
IMO it is not appropriate for 800px-1200px. | Repro steps
Expected
Actual
Screenshots/videos   | Duncan Brain Agreed, although we have said we don't want to design for tablet a better understanding of touch elements would help as as its normally convenient to keep consistent one way or another but tablet kind of needs both (floating action button I like for touch but not desktop a long way to go for mouse) Joyce Sato-Reinhold I just take issue with the idea that 1024+ is still “tablet” (or should be designed for tablet); if 900-1200 or even 1024-1200 were restored to desktop it would make more sense (it’s basically the full width of my laptop). | |
Support: attachment window defaults to "image files" only. | Repro steps
Expected The window should display files of all supported formats by default. Actual The window displays only image files by default. Screenshots/videos  | ||
I am not able to move my chinchillas, house ducks, or other companion animals to my FARMHOUSE/RESIDENCE) (I am contesting the idea that “Residence” should not be a valid destination for animal movement) | Repro steps
Expected
Actual
Note: this is one of the situations that could prompt what Prabjot described below when he said “cannot specify a location for a movement task” and we assumed he had no movement-compatible locations. Residence is a particularly problematic exclusion because it is an AREA LOCATION, not a point or line location like the other excluded locations (gate, water valve, sensor, boundary, etc) and there is no indication to the user why it is not appearing on the map as a selectable location. Screenshots/videos  | ||
Desktop animal inventory is displeasingly proportioned (I do not think our implementation is correct according to the original Figma. As this is the main view of our new feature, I really would like to see it correct and as attractive as possible). | Repro steps
Expected
Actual
Screenshots/videos  | ||
Image uploader should be hidden when empty in readonly mode [Duplicate now with table entry below] | Repro steps
Expected
Actual
Screenshots/videos  | ||
Animals are deselected when returning from the task creation flow | Repro steps
Expected The animals you selected are still selected. Actual The animals are deselected. Screenshots/videos | ||
Add the possibility to filter by retired locations. | Description: Currently when we are on the tasks page, and our farm has some retired locations the tasks that are associated with that retired location and were previously completed or abandoned, will not be displayed on the Tasks page. | ||
Animal type and breed filters include types and breeds that don’t exist on the farm | Repro steps
Expected Only types/breeds that exist on the farm are displayed Actual All default types and breeds are displayed Screenshots/videos | ||
When creating a custom task with animals, I never receive a summary view telling me which animals I have selected (unlike in a movement task). | Repro steps
Expected
Actual
Screenshots/videos | ||
Validation message in sex detail input is unclear | Repro steps
Expected The message should clearly explain that the count needs to be updated, or probably just update it automatically? The only reason count is a separate field is because sex detail is optional, but if the user fills out the sex detail we could easily infer the count and it seems unnecessary to make them update both fields Actual The sex detail input shows validation error “You cannot have more than 1 animal” Screenshots/videos  | ||
If two animals have the same identifier but different tag color there’s no way to distinguish them in the inventory | Repro steps
Expected Animals should be displayed with both the tag number + the tag color in order to tell them apart Actual Only tag number is displayed Screenshots/videos  | ||
[Pre-existing] When abandoning a task, the “Did you enjoy this task?” field shows up and is mandatory | Repro steps
Expected If I’m abandoning the task wouldn’t that mean I didn’t complete it? I’d expect the “rating” field not to show up Actual “Did you enjoy this task?” field shows up and is mandatory | ||
Multiple selection for "Uses" is not specified. | Repro steps
Expected The "Uses" field could specify: Select one or more. Actual The field only displays: Select. Screenshots/videos  PS. Same for ‘purpose of the movement’  | ||
Repro steps Expected Actual | |||
CTAs are pushed to a corner vs being prominent | The ‘+’ for adding animals, edit and delete actionable on animal details page could be more prominent | ||
Location of animal in editing mode should also be editable | While editing animal details, either we make animal location editable or don’t show it at all | ||
Redundant step of selecting animals if a task was started from a selection of animals |
agreed![Jira links]
LF-3566
-
Getting issue details...
STATUS
LF-3792
-
Getting issue details...
STATUS
LF-3828
-
Getting issue details...
STATUS
LF-3872
-
Getting issue details...
STATUS
LF-3972
-
Getting issue details...
STATUS
LF-3951
-
Getting issue details...
STATUS
LF-4115
-
Getting issue details...
STATUS
LF-4356
-
Getting issue details...
STATUS
LF-4538
-
Getting issue details...
STATUS
Known Issues
Sorting by Breed:
Sorting functionality may not work correctly when attempting to sort animals by breed.
UI small bugs
When the total number of animals on the farm is very large, the count may overlap the borders of its display box.
Session Details
Synchronous or asynchronous? | Asynchronous |
|---|---|
When? | 29.11.2024 |
Where to test? |
Bug Reports
Reporter | Description | Details | Pre-existing? | Priority | Blocker? | Also seen by |
|---|---|---|---|---|---|---|
E.g.: Anto Sgarlatta | E.g.: The SSO button is not clickable | E.g.: Repro steps
Expected Should navigate to the Google page to choose an account Actual Nothing happens Screenshots/videos | E.g.: No | E.g.: High | E.g.: Yes | E.g. Joyce Sato-Reinhold |
Users are currently able to create a duplicate of an already existing LiteFarm animal type or breed. | Repro steps
Expected It was expected that on step 7 once the user will try to create an already existing animal type the validation error will be displayed. Actual The duplicated animal type is created. Screenshots/videos | |||||
Case-Insensitive Validation for Animal Types or Breeds | Repro steps
Expected The system should treat animal type and breed names as case-insensitive. Attempts to create duplicates, regardless of capitalization, should trigger a validation error. Actual The system does not perform a case-insensitive check when creating a new animal type or breed. As a result, users can create duplicates with differing capitalization (e.g., "Chicken" and "chicken"). Screenshots/videos | |||||
Missing Validation Message for Duplicate Animal Types or Breeds. | Repro steps
Expected The system should validate animal type or breed entries in real-time during the creation process. If a duplicate is detected, a clear and informative validation message should be displayed immediately (e.g., “This animal type or breed already exists on your farm.”). Actual When a user attempts to create an animal type or breed that already exists, no validation message is displayed during the creation process. Instead, the user encounters a generic error message, “Failed to create Animal or Batches,” only at the final screen. Screenshots/videos | |||||
Cost of Animal Displays Incorrectly for Very Small Decimal Values (e.g., 0.00000001) | Repro steps
Expected The cost should be displayed accurately, maintaining precision up to the required decimal places (e.g., 0.00000001). The system should handle small values gracefully without formatting issues or errors. Denis Dovganyuk does it make sense to allow less than 0.01? Actual When the user enters a very small decimal value (e.g., 0.00000001), the displayed cost is incorrect it actually shows “1e-8” Screenshots/videos | |||||
Checkbox for 'Create Individual Animal Profiles' Becomes Active When Clicking Outside Its Area | Repro steps
Expected The checkbox should only become active or inactive when the user directly clicks on the checkbox itself, not when clicking outside its designated area. Actual Clicking anywhere outside the checkbox area (e.g., adjacent whitespace or nearby text) incorrectly activates or deactivates the 'Create Individual Animal Profiles' checkbox Screenshots/videos | |||||
“Save” Button Remains Active Without Any Changes in Edit Animal Flow | Repro steps
Expected The "Save" button should be disabled until a change is made to the animal details. Actual The "Save" button is active even without making any changes. Screenshots/videos | |||||
Dam and Sire Information Lost When Toggling Between “Brought In” and “Born at the Farm” in Edit Animal Flow | Steps to Reproduce:
Expected The fields “Dam” and “Sire” should retain the information entered during the animal creation process, regardless of toggling between “Born at the Farm” and “Brought In Actual The information in the fields “Dam” and “Sire” is cleared and no longer available after toggling between these options. Screenshots/videos | |||||
Task creation date mismatch between creation and listing page. | Repro steps
Expected The date on the task listing page will be exactly the same as it was during the creation. Actual During the creation of the task I entered Date as ( 12/18/2024) Screenshots/videos | |||||
Finance transactions date mismatch between creation and listing page | Repro steps
Expected The date on the finance transaction list page will be exactly the same as it was during the creation. Actual During the creation of the task I entered Date as ( 11/04/2024) On the downloaded report the Dates will be also one day off. Screenshots/videos | |||||
Preview Image Broken When Non-Image Files (e.g., .xls, .mp4) Are Uploaded | Repro steps
Expected Results: No broken or placeholder preview should appear. This may mislead the user, he may think that the file is not uploaded. Actual Results: When a non-image file (e.g., .xls or .mp4) is uploaded, the preview section attempts to render the file, resulting in a broken or blank preview. Screenshots/videos  | |||||
Animal Movement Purpose Not Retained When Task is Modified and Navigated Back | Repro steps
Expected When a user sets the purpose of movement for an animal and navigates back and forth in the task, the purpose of movement should remain saved and display correctly. Actual The purpose of movement for the animal is lost or reset when the user modifies the task and navigates back to it. Number of animals is updated correctly Screenshots/videos | |||||
Unable to Filter Animals by Gender | Repro steps
Expected Users should be able to filter animals by their gender using the filter options, and the results should display animals matching the selected gender criteria. Actual All animals are shown. No changes applied. Screenshots/videos | Yes | ||||
Animals and batches do not line up well in inventory table. | Repro steps
Expected Lines up Actual Does not line up. If you align text, icons do not align and vice versa. Screenshots/videos 
| |||||
Animal Icon does not appear in main inventory table | Repro steps
Expected Image is seen in main inventory Actual It is not Screenshots/videos | Joyce Sato-Reinhold This has bothered me for literally months | ||||
It is not possible to complete any kind of task if you choose that you have done some changes to the task. | Repro steps
Expected Users should be able to mark tasks as completed, even if the completion date is set to a past date, as long as all other criteria for task completion are met. Actual Tasks cannot be marked as completed if the completion date is set to a past date. An error or restriction prevents the user from completing the task. Screenshots/videos Denis Dovganyuk can you show content of error response from API please (screenshot or paste into description)  | No, checked on the APP and this is not reproducible there. No (Joyce Sato-Reinhold it can’t be pre-existing; the crash is caused by the animal properties) | Yes | Joyce Sato-Reinhold I see this on every task (custom or default) that does NOT include animals. Bit surprised that it would have been working this morning 🤔 I think I even noticed yesterday that the related animal ids properties were included in tasks even when empty… but kind of ignored… anyway they are passed on and crash! | ||
Farm image preview is broken on beta | Repro steps
Expected Thumbnail of your chosen image is shown Actual Broken preview Screenshots/videos  | No | Yes | |||
local (not beta) console error on animalInventory | Repro steps
Screenshots/videos  Duncan Brain it’s the nesting of sectionHeader under Typography component from mui which is by default <p>. You can solve it by making Typography div: <Typography
component="div" sx={{ flexGrow: 1 }}
className={styles.sectionHeader}>
{!isMobile && sectionHeader}
(I think section header moved from text to block level in this PR: https://github.com/LiteFarmOrg/LiteFarm/pull/3544/ – and sorry I totally I did not write it there although that’s when I noticed). Also never checked if changing Typography to div had any effect on styling. | Joyce Sato-Reinhold | ||||
The message “These animals will be archived and accessible for future reference” is displayed when removing animals | Repro steps
Expected ? Actual The message “These animals will be archived and accessible for future reference” is displayed even though the archived animals section hasn’t been implemented yet. Screenshots/videos  | Yes | Joyce Sato-Reinhold The removed animals are even removed from a task that has been completed in the past, prior to their removal date (will make ticket below as it is related). There is nowhere in app where indication of these animals remain | |||
(Related to above) Animals removed from my farm are retroactively removed from completed movement tasks | Repro steps
Expected
Actual
Screenshots/videos  | No | Yes | |||
Animal count should truncate at some pre-decided value | Repro steps
Expected “>54321” is show Actual Cut off screen (good to make the number component predictable max width for all components with nested animal count) Screenshots/videos 
| |||||
Animal batch count should truncate at some pre-decided value | Repro steps
Expected “>54321” is show ? Actual The number is cut off Screenshots/videos  | No | ||||
The shadow on the confirm button in remove animals modal is cut off | Repro steps
Expected The shadow on the confirm button is visible Actual The shadow on the confirm button is cut off Screenshots/videos  Expected:  | No | ||||
Created Custom Task Not Displayed in Crop Plan Task List | Steps to Reproduce:
Expected After creating a custom task, that is associated with the crop plan and which doesn’t have any animals in it should appear under the list of tasks in the crop plan, allowing users to view and manage it alongside other tasks. Actual The custom task, despite being successfully created, does not appear in the crop plan task list, making it inaccessible for users. Screenshots/videos | No, checked on the APP, and there it works as expected. | Yes | |||
Checking “Complete this task now” on custom task results in type error | Repro steps
Expected Go to completion flow Actual Type error Screenshots/videos 
| Yes | Yes | Denis Dovganyuk Also see this, doesn’t depend on the fact if custom task includes Animals or not. Joyce Sato-Reinhold as Denis said, doesn’t require animals & pre-existing (already on app). Jira:
LF-4551
-
Getting issue details...
STATUS
| ||
Switching the “Did you have to make any changes to this task?” option from “Yes” to “No” keeps the edited purpose inputs instead of reverting to the original purpose data in the movement task completion flow | Repro steps
Expected The inputs are reverted to the original data Actual The edited purpose inputs are retained Screenshots/videos | No | ||||
No results are displayed, because previously filters were automatically applied. | To reproduce this issue you should have at least several created in your farm, and they should have some different data. For example different breed.
Expected 1 Batch of animals(ID 1) should be displayed. Actual 0 results are shown Screenshots/videos | No | ||||
It is not possible to complete the movement task if you choose that you have done some changes to that task and also you choose a date in the past. | Repro steps
Expected The task should be completed Actual The task is not completed an error is displayed. Screenshots/videos  Additional information: | No | Yes | Joyce Sato-Reinhold I see this too moving animals that have NO birth or brought in date set on them. I only see it when the time is fairly far back. I wonder if the record created date is coming into play? Or oddly maybe… changing the month? So Dec is okay but Nov errors? Sayaka Ono This happens to custom tasks without animals. What did I do wrong? 🤮 | ||
(Related to the one above)
| Repro steps
Expected A task should be created. Actual Task creation fails. Screenshots/videos | Yes | Joyce Sato-Reinhold What a specific bug 😂 And yes past dates are fine but not more than a month past! | |||
Un-entered breed is shown as “null” on ‘mobile’ view on all languages | Repro steps
Expected
Actual
Screenshots/videos  | No | ||||
Recording a movement task in the past messes up animals' location 😱 | Repro steps
Expected The animals are in location A. Actual The animals are in location B. Screenshots/videos | Yes | Duncan Brain 😱 😱 - makes sense tho | |||
Task date filter doesn’t work as expected | Bug1: Repro steps
Expected The date filter is applied Actual The date filter is not applied Bug 2: Repro steps
Expected The date filter is removed Actual The date filter is still applied Screenshots/videos | No There may be a bug ticket for the date filter | Yes | |||
The app crashes when trying to access deleted animal’s details page | Repro steps
Expected The “unknown record” screen is displayed. Actual The app crashes. (Cannot read properties of undefined (reading 'id')) Screenshots/videos | Denis Dovganyuk Also saw that issue. | ||||
Number of animals in a batch displays as ‘infinite’; failed to create the batch. | Repro steps
Expected Not sure, maybe: ‘number shouldn’t be higher than xxx' before allowing to advance to the next page? Actual Number of animals in a batch displays as ‘infinite' → ‘Failed to create batches’. Screenshots/videos 
 | |||||
Farm worker is able to create an Animal Movement task is it allowed? | Pre execute The farm should have animals created, Farm Worker is not allowed to add animals to the farm Repro steps
Expected It was expected that I won’t be able to create a Movement task as a FarmWorker. Actual The task is created. Screenshots/videos | Hmm, I’m not sure if that’s wrong but there is an inconsistency because Farm Workers do not have the ability to add Movement task by Action Bar > Create Task. If one flow is available to them probably both should be. Joyce Sato-Reinhold | ||||
Animals Are Not Added to Custom Tasks Created by Farm Worker Accounts | Pre execute The farm should have animals created, Farm Worker is not allowed to add animals to the farm Repro steps
Expected When a custom task is created using a Farm Worker account, the selected animals should be automatically associated with the task. Actual When a custom task is created using a Farm Worker account, no animals are associated with the task, even if they were selected during task creation. Screenshots/videos Joyce Sato-Reinhold Wait there is a lot going wrong here!
 | Joyce Sato-Reinhold I think they are added but were deselected in the video there. The lack of highlight and lack of summary component on Custom Tasks is confusing the situation | ||||
The selected animals are not highlighted during the completion of a Movement task. (Farm Worker account) | Repro steps
Expected  Actual Result: Animals are not highlited Screenshots/videos Here how it should be: | Yes | Joyce Sato-Reinhold This is true for movement task creation as well. Animals can be selected and associated with the task, only the highlight is missing. Very interesting. | |||
After submitting the feedback form, the user is redirected to the home page | Repro steps
Expected The user stays at the inventory page Actual The user is redirected to the home page Screenshots/videos | Joyce Sato-Reinhold this is because the pop-up submission modal is defined on the home screen unfortunately | ||||
The information is not updated properly for the farm worker. | Pre - execute: To reproduce this issue you will need to have Farm Worker account and a Farm Owner account associated with the same farm.
Expected The information is updated. Actual The misleading information is shown for a Farm Worker account Screenshots/videos Denis Dovganyuk could you specify that “Navigate to the Farm Worker account” means you have to have both open concurrently (i.e. this is a concurrency bug)? I thought you meant navigate through logout and logging back in, which will not display this behaviour (I saw in the video you had two browsers though) | |||||
Title is missing in the animal details view header | Repro steps
Expected  Actual The title is missing Screenshots/videos | |||||
Removed animals are not displayed in a completed/abandoned task, even though they were included in the task | Repro steps
Expected The removed animal is displayed in the task as a record. Actual The removed animal is not displayed in the task. (Another question, should we null the location of animals when they are removed? The summary table shows animals' current location…)  Screenshots/videos | Yes | ||||
Table header needs to be lowered or KPI higher n z-index. | Repro steps
Expected KPI higher than table header Actual KPI lower than table header Screenshots/videos 
| |||||
Top menu right side may need a hamburger menu at some point | Repro steps
Expected Menu does not underlap logo Actual Screenshots/videos | |||||
The app crashes when attempting to delete animals that have already been deleted (caused by concurrency behaviour, but the issue is that errors are not properly handled) | Repro steps
Expected The error snackbar is displayed. Actual The app crashes. Screenshots/videos | |||||
Personalized image should be used for batch/individual identification in inventory [Duplicate] | Assuming this is a usability suggestion and not an error. Repro steps
Expected After I’ve added a custom image to the animal or batch of animals, I should see that custom image for the animal/batch, instead of the default graphic. Actual default graphic still displays. Screenshots/videos   | |||||
Clicking cancel doesn’t do anything | Repro steps
Expected I should get the standard cancel prompt Actual nothing happens, but the url changes. Eventually the native cancel appears Screenshots/videos | |||||
Multiselect input pills clear button styling offset | Repro steps
Expected Remove icon in pills should be vertically centered The pills also look different from the designs so if we fix them we could possibly update the whole styling? Actual Remove icon in pills is offset Screenshots/videos  | |||||
There’s no “I don’t know” option when editing sex detail | Repro steps
Expected In the general details tab, there should be a way to “remove” the sex by choosing “I don’t know”. Link to design Actual There’s no “I don’t know” option so there’s no way to clear the sex Screenshots/videos  | |||||
Misleading copy in removal modal? [Duplicate] | Repro steps
Expected Not sure Actual There’s a message saying “These animals will be archived and accessible for future reference”, but there’s no way for users to view them right now Screenshots/videos  | |||||
Unhandled error when editing animal birth date | Repro steps
Expected Validation message should be shown before saving or input should disable unallowed dates Actual UI doesn’t handle the error properly, generic error toast is shown and error shows up in console Screenshots/videos  | Yes | ||||
“Click to upload link” should not display or should “look” disabled if not in editing mode [Duplicate - See Usablity section] | Repro steps
Expected When not in edit mode, there should be no “Click to upload” link on the image field, or it should look disabled Actual Click to upload link looks clickable Screenshots/videos  | |||||
o instead of null value for animal sex | Repro steps
Expected The value indicated for the sex of the animals should reflect the most accurate representation Actual The value shown implies that there are 0 females, when that is not accurate.  Screenshots/videos | |||||
Clicking on the “Save” button does nothing. | Repro steps
Expected It was expected that clicking on the “Save” button will cause an error that I have just saw. Actual When you click on the”Save” button nothing happens. | |||||
Default Highlighted Animal/Breed Type Remains Highlighted When Attempting to Select Another Option in Dropdown Menu on mobile phone | Steps to reproduce :
Actual Result: Expected Result:   | |||||
Informative Pop-Up Message Does Not Close on Mobile When User Clicks on "Type Animal" or "Breed" Dropdowns | Steps to reproduce :
Actual Result: Expected Result: | |||||
Creating a new category - it is case sensitive. “Type” and “Breed” | Repro steps:
Expected: Identification of category regardless of case difference or special characters, Actual: Case Sensitivity: "Dog" vs. "dog" "Lab" vs. "lab" Special Characters: "snake," vs. "Snake" "python" vs. "python." | |||||
“This task has already been completed flow” is broken for custom tasks | Steps to reproduce: Select animals > create task > custom task > fill details > select check box “task already completed Expected: Prompt to complete task Actual: Error screen | |||||
Icon against pigs is of cattle | Create animal | |||||
Prabhjot Singh | How do you define the location? | When creating a batch of animals, how does the user define the location of the batch? | ||||
Prabhjot Singh | Adding a task for a batch of animals (chicken) | Trying to add a task “Movement” for a batch of chickens but can’t select anything on the Map | ||||
Prabhjot Singh | Adding sex details of a batch of animals | When Creating a batch of animals and specifying their sex details, it allows us to specify for less than the total. Do we allow that? | ||||
Have to always press enter to ensure the value is stored instead of just clicking out of it when typing in animal type and breed. | Repro steps
Expected: Screenshots/videos Unable to insert video | |||||