Bug Bash - 2024-07-19 Soil Amendment 2.0

Bug Bash Fundamentals

Orientation meeting:
Video linkVideo Conferencing, Web Conferencing, Webinars, Screen Sharing
Passcode: RBU^OY9*

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?

  1. 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.

  2. 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.

  3. 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)

Name

Language(s)

User role(s)

E.g.: @Denis Dovganyuk

E.g.: Spanish, English

E.g.: Farm Owner, Farm Worker

@Duncan Brain

English

Farm Manager

@Joyce Sato-Reinhold

English

Extension Officer

@Larisse Cavalcante

Portuguese

Farm owner

@Sayaka Ono

English

Farm Manager

@Denis Dovganyuk

English

Farm Owner, Farm Worker

@David Trapp

English, Portuguese

Farm owner

@Divya Chayanam

English

Farm Owner

@Joaquín Moreno

English, Spanish

Farm Owner

@Martina Propedo

Spanish

 

Scope

This bug bash will be focused on testing Release 3.6.5. The purpose of the patch is to give our users the possibility to create a detailed soil amendment task. So that they can efficiently plan and document the soil treatment processes and ensure proper execution by the assigned staff.
What is more this release should fix some highly annoying issues that were in the APP for a while, for example the White Screen.

[Jira links]
https://lite-farm.atlassian.net/browse/LF-3884
https://lite-farm.atlassian.net/browse/LF-4213
https://lite-farm.atlassian.net/browse/LF-3946
https://lite-farm.atlassian.net/browse/LF-4029
https://lite-farm.atlassian.net/browse/LF-4225

The main focus of the session should then be on creating the Soil amendment task, creating other types of tasks, visiting the tasks page, deleting the tasks that were created, abandoning the tasks, completing tasks.
We need to be sure that once the user is trying to complete the task he should be able to finish it both by making changes during the completion or not.
For more details on some of the things to assert for, check out the User Stories below.

User Stories

As a (potential) LiteFarm user of any role:

Task Management Guidelines

Viewing and Adding Tasks

  • When accessing the tasks page, you should be able to view any previously created tasks and have the option to add a new task.

Adding New Tasks

  • Ensure that clicking the “+ Add a new task” button allows users to select any task type, including the Soil Amendment task.

  • Copy crop plan should successfully create copied tasks.

Filters Functionality

  • Verify that filters are working correctly by testing different filter options to ensure appropriate results. Be aware of known issues related to displaying tasks from previously deleted areas.

Account Permissions

  • Confirm that FO/FM/EO accounts can still manage custom tasks.

  • Ensure that all users can create any type of task, with the exception that FW accounts cannot create Planting and Transplanting tasks or manage custom tasks. Test by creating various task types, including Soil Amendment tasks.

  • Confirm that all users can create or edit products from within the product-containing flows (soil amendment, cleaning task, pest control tasks)

Task Creation Process

  • During task creation, verify that you can complete the task by assigning it to yourself and marking it as already completed.

  • Ensure the ability to cancel task creation by clicking the “Cancel” button. A confirmation pop-up should appear:

    • Clicking “No” allows you to continue the process.

    • Clicking “Yes” aborts the process, redirecting you back to the tasks page.

  • Ensure that you are still able to create any kind of a task for a wild crop. If you don’t know how to create a wild crop please ask @Denis Dovganyuk

Post-Creation Verification

  • After creating a task, verify that the task information is correct in view-only mode by selecting the newly created task on the tasks page.

  • Ensure that any changes to a task (created, completed, abandoned, deleted) trigger a notification to the assignee.

Task Management

  • Confirm that you can still delete or abandon created tasks.

  • Verify that navigating back and forth during the task creation flow retains previously entered information.

  • Confirm that tasks are correctly abandoned or deleted when management plans are abandoned/deleted

  • Confirm the flow works equally well for built-in tasks and for custom tasks

Documentation of Added Products in Certification Export

  • Should record the quantity of soil amendment products in completed tasks added to organic locations for organic certification-pursuing farms in Record I - Crop Productions Aid of the certification document export

[Link to appropriate sections of the Sanity Script here if there are any] Sanity Script

 

Known Issues

  • We know that the user is able to create the 2 or more custom tasks type with an exact same name.

  • We know that once the user opens the LiteFarm Tab after he has closed his laptop he won’t be able to continue the creation process from the place he stopped.

  • We know that to apply the filter by date range, you need to change another filter setting as well

 

Session Details

Synchronous or asynchronous?

Asynchronous

When?

 

Where to test?

https://beta.litefarm.org/ Beta

Bug Reports

Reporter

Description

Details

Pre-existing?

Priority

Blocker?

Also seen by

 

Reporter

Description

Details

Pre-existing?

Priority

Blocker?

Also seen by

 

E.g.: @Denis Dovganyuk

E.g.: The SSO button is not clickable

E.g.:

Repro steps

  1. Access LiteFarm logged out

  2. Click on the Google SSO button

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

 

@Joaquín Moreno

Deleting a soil amendment task throws an error page

Repro steps

  1. Create a Soil Amendment task

  2. Return to the Tasks page

  3. Click on the task created on step 1

  4. Delete the task

Expected

After deleting a task the user should be sent back to the Tasks page.

Actual

After deleting a task the app shows an error page. After refreshing, the actual updated Tasks page appears.

Screenshots/videos

 

20240719-1709-52.0518653.mp4


Joyce: this was the console error I saw when reproducing this

 

No

Highest

YES!

@Joyce Sato-Reinhold

Thank you for finding Joaquín! I can repro this if I set the measurement type to volume. I’ll add the console error to the details…

 

@Larisse Cavalcante

The error page doesn’t show to me. Instead, I couldn’t click on remove the task. Once I’ve finished the following recording, I was directed to the page with the task list, and the desired task was removed.

@Denis Dovganyuk
I was not able to reproduce the issue.
Haven’t seen any errors and was just redirected back to the Tasks page as expected.

 

@Larisse Cavalcante

Soil amendment creation flow: MISSING translation

Repro steps

  1. Create a Soil Amendment task

  2. Choose the date

Expected

“Selecione o(s) local(is) de adubação e correção do solo:”

Actual

MISSING

 

 

 

 

 

 

@David Trapp

No inline error for character count for “Describe the purpose”

 

2 issues:

  1. Should run a check on character limit, same as notes field, though ideally with reduced character limit

  2. should display an inline error

 

@Joyce Sato-Reinhold wait I’m way more horrified by that TypeError that happens to be in your console in this screenshot (that error has nothing to do with character count) @David Trapp was there a consequence in this situation like not being able to submit the form?

@Joyce Sato-Reinhold yes, I was able to get to the last page of the flow and clicking “Save” did nothing.

 

no

Medium

Yes

@Denis Dovganyuk Was trying to reproduce this issue, and once the user tries to complete the creation of such task( Number of characters in the Describe purpose field is more than 255 )
You will get 400 error.

@Duncan Brain

When assigning a task one option should have in brackets (me) to distinguish between similar names

Repro steps

  1. Have two users with the same name

  2. Go to assign task

Expected

One entry should have (me), or some other distinguiser like email address, beside it.

Actual

Only important in areas where multiple people can have the same name (John Smith, John Smith Jr.)

https://www.ancestry.com
What is the most common full name in the world?

Screenshots/videos

 

 

yes

low

No

 

 

@Duncan Brain

Complete form breaks when not completed fast enough – allowing page to time out or something

Repro steps

  1. Create a Soil Amendment task

  2. Go to complete task and wait on the last form of complete flow with task rating etc. for about 15 mins maybe less

Expected

Should be able to complete form. without following error

Actual

Something goes wrong. But navigating away and back allows the form to complete.

No

Highest

Yes

@Joyce Sato-Reinhold

@Denis Dovganyuk

@David Trapp

 

@Joaquín Moreno

Some typos and improvements for Spanish translation terms

I’m a bit finicky when reading Spanish, so feel free to ignore those suggestions that were already discussed in the past and you reached some consensus.

Expected

  1. “Aditivo de suelo” (current translation for “Soil Amendment”) doesn’t refer to an action (i.e. it has no verb) as it happens with most of the task names. Therefore I would rename it to something like “Acondicionar suelo”;

  2. In “Control de pestes” (current translation for “Pest Control”), “pestes” is incorrect in this context. It should be “Control de plagas”;

  3. When creating a Soil Amendment task and selecting the location, it’s missing the translation “Seleccione la(s) ubicación(es) de la tarea”. In the English version we are being more specific (“Select the soil amendment location(s)”), so maybe the translation should be “Seleccione la(s) ubicación(es) para el acondicionamiento del suelo”;

  4. When adding the product(s) for the soil amendment task, the “remove” button is not translated. It should be “Eliminar”;

  5. When configuring a product for the soil amendment task, there is a typo (“fetilizante” instead of “fertilizante”). The part “del suelo” is redundant and should be removed. The translated line should be “¿El fertilizante está en la lista de sustancias permitidas?”;

  6. When being asked by the workers wages, “modificar” sounds more natural than “alterar” in this context. Also, “cesionarios” is a bit confusing in this context and it should be replaced with “asignados”. So the full line should be translated like “¿Necesita modificar el salario de las personas asignadas a esta tarea?”;

  7. When setting the % of the field to amend, “enmiendas” sounds unnatural in this context (it is more commonly used in law-related contexts). I would translate the line to “% del área a acondicionar”;

  8. Some minor typos. The translation should be “Aplicado al <PERCENTAGE> de sus <FIELD_SIZE> de terreno”;

  9. In the Application rate input, the translation should be “Tasa de aplicación”.

Actual

  1. 1.jpg

  2. 2.jpg

  3. 3.jpg

  4. 4.jpg

  5. 5.jpg

  6. 6.jpg

  7. 7.jpg

  8. image-20240719-185235.png

  9. image-20240719-191326.png

No

Low

No

#4 also occurs in PT

 

@Larisse Cavalcante

Application rate = 0

Repro steps

  1. Create a Soil Amendment task

  2. Select date, location and plan

  3. Input a small quantity to apply

  4. Advanced

Expected

Not sure, but maybe it could show up a message saying that the quantity to apply is too small for the area.

Actual

Application rate=0

Screenshots/videos

 

 

No

Lowest

No

 

 

@Larisse Cavalcante

Translation error

Repro steps

  1. Create a Soil Amendment task

  2. Select date and location

Expected

“Esta tarefa influenciará em algum plano?

Actual

Question mark missing

Screenshots/videos

 

 

Yes

Lowest

No

@David Trapp

 

@Larisse Cavalcante

Override wage for unassigned task

Repro steps

  1. Create a Soil Amendment task

  2. Select date, location and crop plan

  3. Input application method, product and quantity

Expected

Error message: Select an assignee to override their wage

Actual

It’s possible to override the assignee wage for a task that is unassigned

Screenshots/videos

 

Yes

Medium

No

@Denis Dovganyuk This exists for a long period of time, and in my understanding in this case you just change the wage for this task, and than once someone will grab this task, the Wage will be updated.
Because you are not overriding the Wage for the person. Even you are not overriding the wage for the task type. Just for a single task.

Create the Jira ticket and tag Loic

 

@David Trapp

Localization error in numerical representation in total area of application.

Current Behavior: The number is represented as 16.89.

Expected Behavior: The number should be represented as 16,89 according to Portuguese (pt) localization standards.

Steps to Reproduce:

  1. Navigate to the relevant section of the application.

  2. Observe the numerical representation of the value.

Additional Notes: In Portuguese (pt) localization, a comma (,) is used as the decimal separator instead of a period (.).

 

 

No

Low

No

 

 

@David Trapp

Magnetic supplier input field

Repro steps

  1. Create a Soil Amendment task

  2. On the “Tell us about this task” page, add a new product but don’t add a supplier

  3. attempt to input a value in any field that is not the supplier field

Expected

the value is input and you remain in the selected input field

Actual

The value is input but then you are pulled to the supplier input field

 

No

High

Nice to have/No

@Larisse Cavalcante
@Denis Dovganyuk
Also saw such strange behavior
Happens only if that is the newly created product, and you haven’t saved the product before you try to Enter the value in the field Quantity to apply.

 

@Duncan Brain

Product details remain after removing product in complete flow

Repro steps

  1. Create a Soil Amendment task

  2. Go to complete workflow

  3. Delete a product

  4. Add a new product

Expected

Blank product form

Actual

Partially filled product form

Screenshots/videos

 

 

No

Highest

Yes

@Joyce Sato-Reinhold

(And thank you Duncan for deducing this will solve duplicate product entries as well!) @Joyce Sato-Reinhold – as long as no-one plays with the API!

 

@David Trapp

Incorrect Coloration of Area When Selected and Deselected

Repro steps

  1. Go through the task creation flow

  2. On “Select task location(s)” page, select two areas

  3. make to the task details page

  4. Return to the “Select task location(s)” and deselect a location

Expected Behavior: The area should revert to its original color once it is deselected, clearly indicating that it is no longer selected.

Actual Behavior: The area remains in a semi- highlighted state, giving the impression that it is still selected even though it has been deselected.

 

 

Yes

Lowest

No

Create a ticket and tag Loic to understand if that is a bug or not

 

@Sayaka Ono

The placeholder text is displayed in the Fertilizer type input field when it is in read-only mode

Repro steps

  1. Start the Soil Amendment task creation flow.

  2. Select a product that does not have fertiliser type.

  3. Click “Product details”.

  4. Observe the fertiliser type input.

Expected

The input is blank.

Actual

The placeholder text “What type of fertiliser is it?“ is displayed.

Screenshots/videos

 

No

Lowest

No

Create a ticket and Ask Loic

 

@Sayaka Ono

The placeholder text is displayed in the Application method select field when it is in read-only mode

Repro steps

  1. Go to /tasks, and select a soil amendment task that was created before the new feature was introduced.

  2. Observe the Application method select.

Expected

The select is blank.

Actual

The placeholder text “Select…“ is displayed.

Screenshots/videos

 

No

Lowest

No

Ask Loic

 

@Sayaka Ono

The user is able to type in the Furrow/Hole depth even when the view is read-only.

Repro steps

  1. Create a Soil Amendment task with the method “Furrow / Hole” without Furrow/Hole depth.

  2. In /tasks, select the task that was just created.

  3. Observe the Furrow / Hole depth input

Expected

The input is disabled and does not display the placeholder.

Actual

The placeholder text “At what depth was the amendment applied?“ is displayed, and the user can type in a number.

Screenshots/videos

 

No

High

Yes

@Denis Dovganyuk

 

@Sayaka Ono

The text colour of the select element is darker than that of other inputs when it is disabled.

Regression!

Repro steps

  1. In /tasks, select a task that has a select field. (eg. soil amendment, field work etc.)

  2. Compare the text colour with that of the text inputs.

Expected

The text colour is the same as that of other fields.

Actual

The text colour is darker.

Screenshots/videos

 

No

Low

No( Nice to have )

 

 

@Sayaka Ono

In the exported RECORD I document, products from incomplete tasks are included.

Repro steps

  1. Create a soil amendment task for an organic greenhouse or any location where the task’s product is included in the exported documents.

  2. Go to /certification, click “Export”, and select a date range that includes the due date of the created task, then export

  3. Open “Record I- Crop Production Aids”.

Expected

The products from the task that was just created are not included in the document.

Actual

The products from the task that was just created are included in the document.

Screenshots/videos

 

Not sure…

High

Yes?

Test if that is a bug ,if yes than it is a blocker.
Watch on an APP as well.

 

@Denis Dovganyuk

400 error is displayed when the user tries to complete the creation of the Soil Amendment Task

Steps to reproduce:

  1. Open the website https://beta.litefarm.org/

  2. Click on the “Tasks” page.

  3. Click on the “Create new task”

  4. Select the soil amendment task

  5. Go through the creation flow.

  6. Once you will enter in the Task details page Select the purpose “ Other “

  7. In the field “Describe the purpose” enter more than 255 characters

  8. Fill all the required fields > Click on the “Continue” button

  9. Click on the “Save “ button

Actual Result:
The 400 Error is displayed . The task is not created.

Expected Result:
The task is created because no errors were shown during the creation

No

Medium

Yes

 

 

@Denis Dovganyuk

The information in the field Furrow / Hole depth won’t be updated during the task completion

  1. Create a Soil Amendment task with the method “Furrow / Hole” ( you may fill the field or not doesn’t matter )

  2. In /tasks, select the task that was just created.

  3. Click on the “Mark Complete” button

  4. Did you have to make any changes to this task? “ Yes”

  5. Change the Value of the field “ Furrow / Hole depth”

  6. Complete the task

  7. Click on the task that you have just completed.

 

Actual Result
No changes were applied during the completion

 

Expected Result:

The value in the “ Furrow / Hole depth” field should be up to date.


Screencast:

 

 

 



No

High

Yes

4320

 

@Denis Dovganyuk

The white screen is displayed once the user tries to enter the already deleted task( Any type of task ) through the Notifications
That is Regression

Steps to reproduce:

  1. Create the “Soil amendment task” ( Assign the task to yourself)

  2. Click on the task that you have created

  3. Delete the task.

  4. Click on the “Notifications “ icon

  5. Click on the “Assigned tasks” > Take me there

Actual Result :
The white screen is displayed the only way to fix this is to log out or go back using the navigation browser buttons.

Expected Result:

See the screenshot
This screenshot is from the APP

Screenshot_1.png

 

 

 




No

High

Yes

 

 

@Denis Dovganyuk

No inline error for character count for “Product” field

Steps to reproduce:

  1. Start creating the task that requires a product, In my case this is the “Clean” task

  2. Enter in the field “Supplier” a value that I guess more than 255 symbols

  3. Fill all the required fields

  4. Click on the “Continue” button

  5. Click on the “Save” button

 

Actual result :
Nothing happens , after about 30 seconds you ll have those errors in the console.
Failed to load resource: net::ERR_FAILED

Once the user tries to make changes, even it won’t work the task won’t be created.

When we talk about soil amendment task there would be just the 400 error failed to create the “Supplier”
image-20240720-065651.png

Expected Result:
The task is created , or the error message should be displayed what is wrong

 

 

In the video you may see the behavior in the “Soil Amendment “

Yes

Medium

No

Sentry errors:

 

@Denis Dovganyuk

Products that have been created are not sorted alphabetically

Steps to reproduce:

  1. Start the creation of the “Soil Amendment Task”

  2. Click on the “Product” field.

  3. Create several products.

 

Actual Result:

Products are not sorted alphabetically.
Instead of this the newly created product will always be the last one.

Expected Result:

Products are sorted alphabetically

Yes?

Low

No

Tag Loic

 

@Denis Dovganyuk

The user is not able to complete the “Soil Amendment task” after making changes.

Steps to Reproduce:

  1. Create the “Soil Amendment” task with the Weight unit of measurement.

  2. Click on the “Task” that you have just created.

  3. Click on the “Mark Complete” button

  4. Did you do any changes? Select “Yes”

  5. Change the method of measurement to “Volume”

  6. Enter the Value > Click on the “Continue” button

  7. Click on the “Save” button


Expected Result:
The task is completed.


Actual Result
400 error. The task is not completed.

 

 

No

Highest

Yes

 

 

@Denis Dovganyuk

The changes in the field “ Tell us more about the application method” are not Saved after the user completes the “Soil Amendment “ task.

Steps to Reproduce:

  1. Create the “Soil Amendment” task with “Application Method” > “Other”

  2. In the field “Tell us more about the application method” Enter any data or you may leave this field without changes.

  3. Complete the creation flow.

  4. Open the task that you have just created.

  5. Click on the “Mark Complete” button

  6. Did you do any changes? Select “Yes”

  7. Make changes in the field “Tell us more about the application method”

  8. Complete the task

  9. Click on the task that you have just completed.

 

Actual Result:

The changes are not Saved. The information that was entered during the Task Creation will be displayed.

 

 

Expected Result:
An updated information should be displayed.

No

Highest

Yes

4329 this ticket number

 

@Divya Chayanam

Mandatory fields are not clear from a user perspective

Steps to reproduce:

  1. Start a soil amendment task

  2. In “Tell us about the task”, the button “Continue” at the bottom isn’t enabled until all mandatory fields are filled. But there is no indication of which fields are mandatory.

  3. A user might fill some details and wonder why the button is not enabled / clickable

Yes

Low

No

Check with Loic

 

@Divya Chayanam

While adding new product details, the CTA “Save product” should be highlighted

Steps to reproduce:

  1. Start a soil amendment task

  2. In “Tell us about the task”, when adding a new task, the CTAs just beneath the product details are lost among other details. Please make the “save product” button yellow/ same colour as any other enabled button.

Not a bug

Medium

No

Ask Loic

 

@Denis Dovganyuk

The white screen is displayed once the user tries to enter the tabs from the place he left after he Restarts his Laptop(PC)

Steps to reproduce:

  1. Open the websitehttps://beta.litefarm.org/

  2. Create the task ( I created “Soil Amendment task” but I believe it doesn’t matter.

  3. Click on the task that you have created and complete this task.

  4. Click on the Task that you have just completed.

  5. Restart your PC ( Laptop) the browser should have the setting to start from the place you left.

  6. Open the browser again

 

Actual Result:

The white screen ( Modal ) is displayed and the user is not able to continue, once he tries to go “Back” nothing happens , the only way is to open another tab.

 

 



Expected Result:

I expected to continue from the place I left.

No?

High

Yes

It may be fixed by another ticket

 

@Denis Dovganyuk

The information in the field won’t be updated once the user completes the Soil Amendment task and changes the Application method

Steps to reproduce :

  1. Create the soil amendment task

  2. Open the task that you have created

  3. Click on the “Mark Complete” button

  4. Did you do any changes? “Yes”

  5. Change the “Application Method”

  6. Complete the flow.

  7. Open the task that you have just completed.

 

Actual Result:

The information in the Field “Application Method” remains the same as during the creation

Expected Result:

It was expected that the information would be updated

No

Highest

Blocker

 

 

@Martina Propedo

detail: quantity does not include litres or other measure of liquids

 

 

Yes

 

No

Make a ticket to update other flows

 

@Martina Propedo

doesn’t allow to “continue” while including tasks

 

 

 

No

 

 

This ticket will be created once we will have more details

 

@Duncan Brain

Form errors found on readonly page

Steps to reproduce :
1. Navigate to readonly task
2. Open console

Expected: no errors

 

 

No

Low

No

Create a ticket for this as well

 

@Denis Dovganyuk

Clicking on the “Product details” drop down button interupts the edit process of the product

Steps to reproduce:

  1. Start creation of the “Soil amendment task”

  2. Go through the flow until you will see “Tell us about product” page

  3. Select the product from the list

  4. Click on the “Product Details” button

  5. Click on the “Edit product details” button

  6. Click on the “Product details” button 2 times.

 

Actual Result:
when the user tries to close the product details during the creation of the new product it is not possible.
However when he clicks on the same button during edit of the product, all the changes are not saved, and he actually cancels the process.

Expected Result:
It was expected that this would only summarize the information about the product, the information should neither be saved nor changed, as a user I just wanted to see how many more fields I had to fill in to finish creating the task.

No

Low

No

Tag Loic

 

@Denis Dovganyuk

There is no confirmation pop up message once the user clicks on the “Cancel” button during creation of the new product.

Steps to reproduce:

  1. Start creation of the “Soil amendment task”

  2. Go through the flow until you will see “Tell us about product” page

  3. Select the product from the list

  4. Click on the “edit” button

  5. Start making some changes.

  6. Click on the “Cancel” button

 

Actual Result:

Once the user clicks on the “Cancel” message all the information is not saved.
As far as I know we want to give a double chance for a user not to lose his progress, that is how we do this through the app.

 

Expected Result:

It was expected that the pop up message will be displayed, and in this case it will say something like: You are going to discard all the changes, are you sure?


No

 

No

Not a bug

 

@Denis Dovganyuk

The translation for a buffer zone location is not working properly during creation the “Soil Amendment” task

Pre - execute:

To reproduce this issue you will need to have at least one buffer zone on your farm

 

Steps to reproduce:

  1. Start creation the soil amendment task for a buffer zone( single area)

  2. When you will arrive on the page “Tell us about task” take a look on the information under the quantity to apply field.

 

 

No

HighNot a

Yes

 

 

@Denis Dovganyuk

(Usability Suggestion)
It is not possible to select several purposes simply by selecting them one by one, you will need every time to click on the “Drop Down” menu

Steps to reproduce:

  1. Start creation the soil amendment task for a buffer zone( single area)

  2. When you will arrive on the page “Tell us about task” click on the “Purpose” field, and try to select several purposes.


Actual Result:

When the user wants to select more purposes he needs every time click on the drop down menu.

Expected Result:

Once the user clicks on the drop down menu he should be able to select 2 or more purposes by selecting them from the drop down menu. To close it the user should click outside the area or on the arrow.

 

 

No

 

No

Not a bug

 

@Denis Dovganyuk

The user that is searching for a certifier is able to create or complete the “Soil amendment” task without filling the “Supplier” field, only if the Product was created before he applied for certification

Steps to reproduce:

  1. As a farmer without certification create one or more products without entering any data in the “Supplier” field.

  2. Apply for a Certification

    1. Click on the “Certifications” button

    2. Choose the type of certification

    3. Choose the certifier if you have any

    4. If don’t have just enter the certifier you want( Any Value)

    5. Complete the flow

  3. Return now to the Tasks page.

  4. Start creating the new “Soil Amendment Task”

  5. Select the Product that you have created on the “Step 1”

  6. Complete the creation flow.

 

Actual Result:

The task is created, even without filling the Supplier field.
After this the user is able to complete this task.


Expected result:

The creation should fail, the supplier field is required.

No

Medium

No

Tag Loic

 

@Denis Dovganyuk

The product is not created(400error) if the supplier name is single "Space" or plural Spaces.
OR
When the Product name is single or more spaces

Steps to reproduce:

  1. Start creation the “Soil Amendment” task

  2. Once you will enter the page “Tell us about product” please enter in the field “supplier” or “product” single space, or you can make it separately( only Supplier field is a single Space”

  3. Try to Save a product

Actual Result:

400 error is displayed.

 

 

Expected Result:
The product is saved, or the descriptive error message is displayed.

No

Low

No ( Nice to have )

 

 

@Denis Dovganyuk

When the user clicks on the drop down menu of the field "Application rate"  during the completion of the “Soil amendment task” the site layout jumps

Steps to reproduce:

  1. Create the Soil Amendment task”

  2. Open the Soil Amendment task” that you have just created.

  3. Click on the “Mark Complete” button

  4. Did you have to do any changes? Yes

  5. Scroll down and click on the Drop down menu near the “Application rate” field.

Actual Result:
The site layout jumps.

 

 

Expected Result:

The website Layout should not jump

No

Low

No

 

 

@Denis Dovganyuk

The text overlaps the borders of the "save" button on mobile device

  1. Start creation the “Soil Amendment task “ on your mobile device.

  2. Go through the flow once you will enter the “Tell us about your task” page.

  3. Start creation of the new product or just edit the one that you have created earlier.

 

 

 

No

High

Yes

@Joyce Sato-Reinhold

 

@Sayaka Ono

For the mobile view only it might be too much to have name and NPK all in select option. And there should probably be some padding between the end of product name and "N".

 

 

 

 

No

Low

No(Nice to have)

@Joyce Sato-Reinhold

Tag Loic

 

@Denis Dovganyuk

If the user changes the Application method before “saving the product details” they will be auto discarded.

Steps to reproduce:

  1. Start creation of the “Soil amendment task”

  2. Go through the flow and once you will see the “Tell us about your task” page.

  3. Select the product or create the new product.

  4. Click on the “Edit product details” button

  5. Start making changes.

  6. Change the Application Method.


Actual Result:
The changes are not saved

 

 

Expected Result:

It was expected that once the user changes the Application method, the information in the Tell us about your product section will not be both Saved or Discarded. Just remain in the same position.

No

Medium

No(Nice to have)