QField Feature Requests

Currently, only one photo can be taken per input. The workflow is currently: Set the 1st point Open the attachment widget, Create and save environment photo 1 Create and save environment photo 2 ... Add detail photo 1, save ... Set the next point. I'd like to take multiple photos with the same attributes (except for the path). So z.B. Set 1st point Open attachment widget Create and save environment photos 1-5 Create and save detailed photos 1-3 set the next point.

As a QField project designer, project manager, and field surveyor, I would like additional functionality from the temporal controller to improve the review, interpretation, and quality assurance of data both in the field and the office. User Interface While in Browse Mode: Temporal Filter Toggle An on/off toggle button should be available under the burger menu (similar to the location of Digitizing Settings when in Digitising Mode). Temporal Filter Controls When enabled, temporal filtering controls should appear as an overlay at the top of the map canvas. Filter Types The temporal controller should support three filter types: 'Calendar' | 'Rolling' | 'Custom' Switching between filter types should automatically update all associated controls and temporal ranges. 3.1 Calendar Filter The Calendar filter is intended for reviewing records by calendar periods. The following controls are displayed: 3.1.1 Period Selector with options: | 'Current' | 'Previous' | '[N] Ago' | Where: Current refers to the current calendar period. Previous refers to the immediately preceding calendar period. '[N] Ago' uses a spinner control allowing the user to select any value ≥ 2 and refers to a single calendar period offset from the current period by N units. For example, '2 Ago' + 'Months' would refer to the calendar month two months before the current month. 3.1.2 Time Unit Selector with options: | 'Day' | 'Week' | 'Month' | 'Year' | All periods are based on calendar boundaries. Examples: Current Month Previous Week 10 Days Ago 3 Years Ago 3.1.3 ☐ 'Include subsequent records' checkbox Displayed only when 'Previous' or '[N] Ago' is selected and controls whether the filter applies only to the selected calendar period or to the selected calendar period and all subsequent records up to the current date. For example, when enabled with the current date of 02 Sep 2026 and '2 Ago' + 'Years' selected, the filter would start on 01 Jan 2024 and end on 02 Sep 2026, but if it was disabled with the same options then the filter would start on 01 Jan 2024 and end 31 Dec 2024. 3.2 Rolling Filter The Rolling filter is intended for reviewing records over continuous periods relative to the current date. The following controls are displayed: 3.2.1 Duration Selector | 'Last [N]' | Where N is selected using a spinner control allowing the user to select any value ≥ 1 3.2.2 Time Unit Selector | 'Days' | 'Weeks' | 'Months' | 'Years' | Examples: Last 7 Days Last 12 Weeks Last 18 Months Last 5 Years The filter range is automatically calculated relative to the current date and time. For example, if the current date is 02 September 2026: 'Last 42' + 'Months' would display records from: 02 Mar 2023 → 02 Sep 2026 No additional "Include Later Records" option is required, as rolling periods inherently extend to the present date. 3.3 Custom Filter The Custom filter provides full manual control over the temporal range and includes an enhanced version of the QGIS temporal slider (similar to the existing proposal at https://ideas.qfield.org/app-feature-requests/p/temporal-controller ). 3.3.1 Filter controls The following controls are displayed: | [Filter Start] | [double-ended temporal slider] | [Filter End] | The filter start/end values would use calendar and time picker widgets. A dual-ended slider should: Automatically update when the start or end date-time is adjusted. Automatically update the date-time widgets when the slider is moved. Be constrained either by: a project-defined minimum and maximum temporal extent specified in QGIS Project Properties; or the minimum and maximum dates present within temporal controller-enabled layers. Changes made using any filter type should automatically update all other temporal controller widgets to reflect the resulting temporal range. The Custom filter is the only filter type that exposes direct time-of-day controls. This allows users to analyse data at sub-daily resolutions where necessary. 3.4 Time-of-Day Filtering For Calendar and Rolling filters, the default filter period should always cover the full day: 00:00:00 → 23:59:59 This simplifies common field-survey workflows and avoids unnecessary complexity. Where time-specific filtering is required, users can switch to the Custom filter type. QGIS Integration Ideally, the same functionality should be implemented within QGIS so that project designers, analysts, and field staff have a consistent temporal filtering experience across both desktop and mobile platforms. This would ensure that temporal filters configured and tested in QGIS behave identically when used in QField.

Sometimes when I log in to the app, I seem to be logged in, but I'm actually not. Only after collecting data and trying to synchronize does the app show a message saying that I'm not logged in. It would be great if this information were very clear on the app's home screen!

As a QField project designer, manager, and field surveyor, I would like to be edit multiple features more efficiently. Currently, when a feature list is open and contains multiple features, if the burger menu is selected then an option to 'Toggle Feature Selection' is at the top of the options. When enabled, individual features can be selected. Once one or more features are selected, the user currently has to select the burger menu again to select the editing option, e.g. Delete, Duplicate, etc. It would be a better UX to first have the toggle appear next to or even in place of the burger menu, and then when at least one feature is selected, the menu opens (would be best displayed as buttons in the list header) with the same options that are in the current burger menu, e.g. Delete, Duplicate, etc. It would save extra taps on the interface.

As a QField user and project creator, I want to be able to visualise certain distances either side of a line that I am digitizing. This would allow for more efficient survey planning using QField. For example, I am undertaking a bird survey where I want to approach every point within a given area to within 100 m. I have a line layer that I will use to plan my route. It has been programmed to display the line drawn as well as a 100 m buffer area around it (once committed). The issue with this is that the buffer cannot be viewed while digitizing — the user must save the feature first — which results in a lot of trial and error while trying to ensure the line drawn remains 100 m apart at all times. By adding a toggle and associated settings (buffer distance in meters) underneath the digititizing settings menu on the map canvas, the experience could be improved greatly. Ideally, the symbolisation of the buffer would be ~30-40% opaque and change colour for areas that overlap. Alternatively, implementing a 'barrier' (anti-snapping, where lines must remain apart by 2 x the buffer distance) option as a toggle would be even better.

Search bar allow to make calculations and keep the result to paste it elsewhere. This functionality isn't available anymore when a subform is open, or a form in fullview mode. It would be glad to be able to make those kind of calculations inside numeric fields for example.

Currently, any user with access to a synchronized project in QField can use the “Send compressed folder to...”/“Send to” function to package the entire project (or individual datasets) and send it by email, messaging or another app, without any control from the server. This completely overrides the access control that is configured in QFieldCloud (users/passwords, roles), since once the data is synchronized locally, there is no way to prevent it from leaving the device. Proposal: Add a project/role level permission in QFieldCloud (e.g. an allow_local_export flag or similar, configurable by the administrator from the project's users/role management panel) that, when synchronized with the device, communicates to QField if the user is allowed to use local export functions (“Send to”, “Export to folder”, “Send compressed folder to”). If disabled, those options should appear locked/hidden in the project menu within QField for that user. Why it's feasible: It doesn't require DRM or complex encryption — it's just another permission, similar to those that already exist to edit/add/delete features. The server already controls other permissions per role; extending it to “export/share locally” would be consistent with that architecture. If a user changes roles and logs back in, the new permission would normally be applied at the next synchronization, as is the case today with other permissions. Use case: I manage my own QFieldCloud with sensitive field data. I need to be able to restrict which users can take copies of the project from their devices, without relying on third-party MDM or purely organizational policies.

We are using Qfields to add new symbols on field. And rotation for those symbols is quite important. At the moment I only can add rotation as a numeric data in forms. If there would be an option in future to add this data graphically, that would be a big help for us.

Actualy, only form view is available, for somme use cases tabular view could be nice. For exemple we would be interested in using Qfield for flow speed measures and need to see all data recorded at a time with conditionnal formating. It will give to operator immediate infromation on data quality and perform more measures if needed.