E.g.: Denis Dovganyuk

E.g.: Spanish, English

E.g.: Farm Owner, Farm Worker

Duncan Brain

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

Joaquín Moreno

English, Spanish

Farm Owner

Martina Propedo

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?

Medium?

No?

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?

no

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
https://www.quora.com/What-is-the-most-common-full-name-in-the-world

Screenshots/videos

yes

reminder you do not need to fill this in yet

reminder you do not need to fill this in yet

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.

Joyce Sato-Reinhold

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

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

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

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

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.

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

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

Larisse Cavalcante

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

Screen Recording 2024-07-19 at 4.12.06 PM.mov

Joyce Sato-Reinhold

(And thank you Duncan for deducing this will solve duplicate product entries as well!)

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.

Legacy select color issues on map.mp4

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

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

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

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

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…

@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

?

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:

Video_240720091645.mp4

No

High

?

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

Video_240720092847.mp4

No

High

?

Denis Dovganyuk

No inline error for character count for “Product” field
Actually that made Beta down

Steps to reproduce:

Image Added