E.g.: @Denis Dovganyuk

E.g.: Spanish, English

E.g.: Farm Owner, Farm Worker

@Duncan Brain

English

Farm Owner

@Joyce Sato-Reinhold

English, Punjabi

Farm Worker, Extension Officer

@Sayaka Ono

English

Farm Owner

@Divya Chayanam

English

Farm Owner

@Navdeep Dhammu

English, Punjabi

Farm Owner

@Denis Dovganyuk

French

Farm Owner, Farm Worker

Asynchronous

https://beta.litefarm.org/ Beta

E.g.: @Anto Sgarlatta

E.g.: The Upload 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. @Joyce Sato-Reinhold

@Duncan Brain

Add task button still missing from locations tasks tab - where is that ticket again?

The add a task floating action button is still missing. I cannot find the ticket for it.

Yes

High

@Joyce Sato-Reinhold

Farm worker shown manage ESci Link, but doesn’t have that section in Farm Settings

Farm Worker sees link at the bottom of the sensor readings:

Open

But doesn’t have the Addoon Partner section in Farm Settings, since they can’t edit / add Partners:

Open

No

low

@Joyce Sato-Reinhold

Farm Worker cannot see the full list of Ensemble Sensors

Farm workers have no way to access the full list of sensors as the link to the full sensor list exists only in Addon Partner block of Farm Settings, and in Map > Add Location > Sensor.

Farm works have permissions to view the full list of sensors, but no access to either of the above.

read above issue

@Joyce Sato-Reinhold

Columns on Field Technology don’t line up

Offset of 2nd + 3rd column will vary depending on the letters in the ESID

Open

@Sayaka Ono

When inviting a user, the page is reload

Repro steps

1. Go to /people

2. Click on the Invite User button

Expected

The “invite a user” form is displayed seamlessly.

Actual

The app refreshes. (The URL becomes /invite_user?. The button type is probably submit?)

Screenshots/videos

Open

Yes

low

@Joyce Sato-Reinhold

Icon on the Field Technology tab indicates the ability to reload (maybe?), but it’s not clickable

Open

Could totally be mistaken here, but the clock with arrow makes me think I can refresh the data by clicking on it; yet in fact icon is not clickable.

(This might be my misunderstanding/mis-reading of the icon)!

med

@Joyce Sato-Reinhold

Depth is displayed with a very high level of precision on imperial farms!

Open

(cm → inches depth conversion is not rounding in KPI)

Correct in list view:

Open

No

Joyce to be looking into this

@Divya Chayanam

Map zoom level when sensor added for first time

Ideally, the zoom level if we are looking at map with an intention to view added sensor, it should be zoomed in

Steps:

1. Map > Add sensor > Add org id

2. List of sensor > click ‘see on map’ for any sensor

Intended result

See the sensor in the map at a closer zoom level

Actual result

Map is quite zoomed out

Yes

Not an issue

@Joyce Sato-Reinhold

No way to get from ESci sensor list to sensor readings view

Including for prioritization because this was brought up by 2 out of 2 developers who didn’t work on the feature

https://lite-farm.atlassian.net/browse/LF-4801


Steps to reproduce:

1. Navigate to the full list of Ensemble sensors

2. Click on everything (ESID, record, see on map)… no way to get to sensor readings view

3. (Need to return to farm map and click on an icon to get to sensor readings view)

Expected result:
“See on map” sensor icon or record in sensor list view table routes to that sensor’s data

No

High

@Sayaka Ono

Sensor list is sometimes empty for a while after connecting to Ensemble

It doesn't always happen, and I'm not sure when this happens. It took a few tries to capture this, but I've seen longer delays than what's shown in the recording.

Open

No

low

@Divya Chayanam

Confusing user journey for soil sampling

Soil sampling flow, if initiated from tasks, can be improved.

Steps:

1. Go to tasks > soil sampling

2. You have no soil sampling locations ‘create new’. Clicking on that takes user to map.

3. As a user, I am zooming in and clicking inside a field, expecting to be picking soil sampling locations. It is only after I click a field, I realize that I should have clicked on ‘add location’ again to add soil sample locations. Is it possible to fast forward one step and directly go to the next step of adding the location?

No

Not an issue

@Divya Chayanam

Map locations in a soil sampling task

It is good to show all locations in a soil sampling task, while making only sampling locations ‘selectable’. This helps a user understand which sampling locations belong to which field. Since there is no other association of a sampling location with a field, this step becomes important. Filter at selection, not at display.

No

High

Ensemble

Sensor KPIs + sensor readings tooltips should be to one decimal place, not two

Requested on call Monday June 9, 2025

med

Ensemble

Show irrigation system name somewhere on the sensor list, e.g. alongside profile (array) name

Requested on call Monday June 9, 2025

Open

E.g.: @Anto Sgarlatta

E.g.: The Save button is disabled.

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

@Denis Dovganyuk

400 Error When Saving Soil Sample Task with Decimal Value

Environment : Beta

Repro Steps
1. Open the website https://beta.litefarm.org/
2. Login with your personal account that has a “Soil Sample” location or create a “Soil Sample” location
3. Navigate to the tasks page
4. Create a Soil Sample task.
5. In the field “Number of samples per location” enter a decimal value ( for ex. 1.4)
6. Fill all the required fields
7. Click on the “Continue” button
8. Click on the Save button

Actual Result:
User receives a 400 error when attempting to save a Soil Sample task that includes a decimal value.

Expected Result:
Decimal values should not be allowed, in the field “Number of Samples per location”. Once you enter the value that has a decimal a field validation error should be displayed.

Open

Content of 400 message:

Open

No

Highest

Yes

@Joyce Sato-Reinhold I’ll add the 400 to the context. It’s a descriptive model validation error so backend could be left as is

@Denis Dovganyuk

Broken Mobile Layout During Soil Sampling Task Creation Flow

Steps to reproduce:

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

2. Login with your personal account that has a “Soil Sample” location or create a “Soil Sample” location

3. Navigate to the tasks page

4. Create a Soil Sample task.

Actual Result:

The website layout breaks or becomes misaligned when the user initiates the Soil Sampling task creation flow on a mobile device.

Expected Result:

The layout should remain responsive and properly formatted throughout the Soil Sampling task creation flow on mobile devices.

Open

No

Low

No

@Duncan Brain

Is this usability?

Soil water content graph not discernible for North | Sensor array

Open

Also full year for temperature and SWC:

Open

No

Low- medium

No

@Duncan Brain

Render lag/flicker for irrigation tab and soil sample task type tab.

Thought I fixed but still present…

Go to task type selection page, or field with irrigation tab for the first time. See the new tiles or tabs pop in a half second later.

No

Low

No

@Denis Dovganyuk Saw that as well.

@Duncan Brain

Adding an image to the animal batch overlays on top of default image

No

Low

No

@Denis Dovganyuk

Latitude and Longitude of Soil Sampling Location Can Be Changed via API Tool

Steps to reproduce:
Actual Result:
The latitude and longitude of a Soil Sampling location can be modified using an API tool, bypassing UI restrictions.

Expected Result:
Latitude and longitude should be immutable once a Soil Sampling location is created, and changes should not be allowed via API.

Yes

Med

No

@Denis Dovganyuk

Concurrency Issue: User Can Edit or Delete an Already Deleted Soil Sample Location

Steps to reproduce:

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

2. Login to your farm on 2 accounts that has a Soil Sample location

3. Navigate to the “Map” page using both accounts.

4. Using Account A - Delete the Soil Sample location

5. Using Account B - Try to do the same.

Actual Result:
User is able to edit or delete a Soil Sample location that has already been deleted by another session or user, leading to inconsistent behavior or errors.

Expected Result:
Once a Soil Sample location is deleted, it should be locked from further edits or deletions. Attempts to modify it should return an appropriate error message (e.g., "Location not found" or "Already deleted").

@Denis Dovganyuk what errors would result? Would the location just not be deleted for both users?

Adding some more context This is true for all locations as far as I can see:

• If user A retires the location, and user B is on the map already, they can edit the deleted location, which UNDELETES it!

• They could also just delete it again but that would be functionally silent.

• It’s a bit weird but I don’t know if it’s the worst UX, it’s not very disruptive, it’s just the latter action will win out
  
  

Yes

not a bug

No

@Joyce Sato-Reinhold

Updated with some more details. This is actually a property of locations, nothing particular about soil sample, but it’s a bit wild. I don’t know if we’ve ever discussed this and maybe even decided we like this UX?

@Joyce Sato-Reinhold

Sensors not visible if clicking on Map immediately after logging in

There is a lag between logging in and getting back the full list of devices that means you have to nagivate away from map and back to see them:

Open

(No issue if you pause before entering map)

No

-

No

@Joyce Sato-Reinhold

Sensors not immediately purged upon changing farms (surprisingly)

Variant issue of the above.

Steps to reproduce:

1. Log onto a farm with sensors

2. Switch farms to another farm with sensors (this is not a likely case in the project!!)

3. Immediately visit map

Result:

Original farm’s sensors persist, but can’t be clicked on (since they don’t belong to the new farm).

As above, waiting or leaving the map and returning will refresh the sensor list to the correct (new farm’s) sensors

Open

No

-

No

@Sayaka Ono

Soil sample task complete view needs styling adjustment

“Number of sampling locations” input is too close to the radio button above.

Open

NO

Low - med

No

@Joyce Sato-Reinhold

NO EMAILS

(Included for prioritization discussion)

https://lite-farm.atlassian.net/browse/LF-4842

Yes

Highest

Yes

@Joyce Sato-Reinhold

Both selected and de-selected visual map icons overlay for soil samples

Steps to reproduce:

1. Create a soil sample task and select one or more sampling points

2. Continue the flow to next screen

3. Go back to remove one sampling point

Result:
Selected icon remains underneath deselected icon, as they are slightly offset and different shapes

Open

YUCK!

No

Med

No

@Sayaka Ono

Sensor array names (?) are missing in Field Technology tab

Open

From @Loic Sans: The original design shows subheading for each type of sensors (arrays vs standalone), also the tab design reinforce the separation from the sensor table, see:

Open

No

Med

Yes

@Sayaka Ono

Data for the last day in the sensor reading date range is not included as expected

At 10 AM on June 6,

[last 7 days] the last data point is from 11 PM on June 5. Today’s data is not included.

Open

[Jun 6 - Jun 6]

Open

[Jun 6 - Jun 7]

Open

This behaviour could change when the ESci API bug is fixed. (https://lite-farm.atlassian.net/browse/LF-4789)

No

low

No

@Joyce Sato-Reinhold I saw this too! Today is included in “This week” but not “Last 7 days”

@Sayaka Ono I feel like the actual date range for “Last 7 days” is wrong… today is Jun 6, so the range should be May 31 - Jun 6, but the request is for Jun 1 - 7…

@Joyce Sato-Reinhold

Latest reading time doesn’t match between Field Technology and Sensor Readings view

Last column of Field Technology time is unlabeled, but I assume it means latest reading time? (I guess another way to look at this bug is that the Field Technology tab could have row headers. Is it maybe “last seen”?)

Whatever this value is, it doesn’t match the latest reading time that you see when you click on the record.

Open

No

Med

No

@Divya Chayanam

Field has unintended irrigation tab

Steps:

1. Create a new field in map. Draw > confirm

2. In the map screen that comes after new field is created, add sensors

3. The new field has the ‘irrigation’ tab even though the sensors are not closeby or associated with this field anyway

4. Open

   

    

No

Not an issue

No

@Duncan Brain This is mocking behaviour and not a bug. The mock chooses the last created field. Irrigation prescription pieces will be commented out prior to first release for sensors and soil task.

@Divya Chayanam

Issues in custom date range filter for sensor readings

The filter range is from 7 April to today, the graph starts from May 1.

Open

No

Med

No