Skip to content

Releases: hotosm/tasking-manager

v5.5 OSM Sandbox

24 Feb 09:17
b157ba2

Choose a tag to compare

OSM Tasking Manager – Sandbox Production Release 🌐

This release publishes the Sandbox feature to the production instance of the Tasking Manager.
• Sandbox PR: #7133
• Discussion: #7148

HOT's Sandbox implementation builds on development from the OSM US Tasking Manager and introduces a controlled, isolated environment for onboarding, practice projects, and projects involving private or sensitive data that should not be published to OpenStreetMap.

Key Use Cases

  • Safe environment for onboarding and contributor training without impacting live OSM data
  • Supports guided practice sessions and workflow familiarization
  • Enables pilot and test projects before production launch
  • Supports private, restricted, or sensitive datasets that must not be published to OSM
  • Suitable for internal-only mapping and experimental initiatives

Working with Sandbox

How can Sandbox projects be identified?

You can filter Sandbox projects in both the Explore and Manage sections. Clear visual cues are also displayed throughout the workflow to distinguish sandbox project.


Explore Filter

Manage View

Workflow Visual Cue
At what stage can a project author choose between Sandbox and Production?

Environment selection happens during project creation. When cloning a project, you can also choose the target environment.


Environment selection during Project Setup
Can the project environment be modified after creation?

No. Once created, a project cannot be switched between Sandbox and OSM database.

Which editors are available in Sandbox projects?

Only the iD editor is enabled for sandbox projects.

Can Sandbox project priority be changed?

No. All Sandbox projects default to low priority, and this cannot be adjusted.

What happens to Sandbox data?

Sandbox data will be flushed monthly.
If you need your Sandbox project data preserved, please raise a ticket here and we will follow up.

Future improvement: We plan to introduce a feature to download project-specific Sandbox data prior to cleanup.

A big thanks to everyone who contributed to development, testing, review, and stabilization of this release 🙌


Other notable improvements in this release include:

Expand to see detailed codebase changes 🖥️

Full Changelog: v5.4.1...v5.5

v5.5 Hotfix

24 Feb 13:35
41ebbab

Choose a tag to compare

Hotfix: Fix Contributions Page Crash for Sandbox Projects

Related issue: #7177

Fixed a crash on the Contributions page for sandbox projects that occurred when a user’s preferred editor was set to anything other than the iD editor.

Contributions page was not properly handling non-iD editor preferences in sandbox contexts, which caused it to fail during rendering.

What's Changed

Full Changelog: v5.5...v5.5-hotfix

v5.4.1

16 Jan 07:40
5cc5c91

Choose a tag to compare

v5.4.1 release focuses on improving everyday usability across the platform.

👥 Contributions & User Data

🧭 Interface & Usability

Expand to see detailed codebase changes 🖥️

New Contributors

Full Changelog: v5.4.0...v5.4.1

v5.4.0

30 Dec 14:45
1ca4020

Choose a tag to compare

👥 User Profile Deletion

Tasking Manager v5.4.0 introduces user account deletion controls, enabling both self-service deletion and administrator-initiated deletion of user profiles.

  • Self-deletion: Users can now delete their own accounts directly from their profile settings. This supports better privacy control and compliance with data protection expectations.
  • Admin deletion: Administrators can delete user accounts when required (e.g., inactive users, policy enforcement, or support requests), ensuring cleaner user management across the platform.

What's Changed

Full Changelog: v5.3.3...v5.4.0

v5.3.3

05 Dec 14:56
6ec4319

Choose a tag to compare

This release focuses on preventing comment loss during navigation, improving task validation tracking, and refining roles & team management, along with several backend stability fixes.

⭐ Key Highlights

Prevent comment loss on navigation

Users will now see a confirmation pop-up if they attempt to leave a page with an unposted comment. This helps prevent accidental data loss during reloads or navigation.
(Related: #6684)

Validator ID added to Task JSON

A new validatedBy attribute has been added to task JSON, allowing visibility into which user validated a task directly from the task grid. (Related: #6954)

Expand to see detailed codebase changes 🖥️

Full Changelog: v5.3.2...v5.3.3

v5.3.2

25 Nov 11:43
5b26e05

Choose a tag to compare

What's Changed

Full Changelog: v5.3.1...v5.3.2

v5.3.1

13 Nov 17:31
9164e32

Choose a tag to compare

This release resolves several long-standing user-reported issues that significantly improve team management, contributor insights, and the overall usability of the Tasking Manager.

  1. Order project contributors by mapped/validated tasks (#6987)

    Project managers can now sort contributors by mapped, validated, or combined task counts.
    This helps quickly identify validators, assess quality, and monitor mapping patterns—especially in large projects.

  1. Remove non-functional density layer (#6755)

    The outdated and broken Density basemap used during project creation has been removed.
    This avoids confusion, prevents blank map displays, and prepares the interface for a future integration of a reliable, high-resolution population density layer.

  1. Enable team deletion without manually finding all linked projects (#6773)
    Teams can now be unlinked more efficiently, enabling deletion without manually tracking historical project associations. The backend now supports controlled unlinking with safety checks to avoid permission misconfigurations.

  1. Add project ID column on project list view (#7005)
    The Project ID is now visible in the list view, making it easier to:
    • Quickly locate specific projects
    • Verify order when sorted by “New”
    • Reduce naming confusion across similar projects
    This aligns UI output with CSV exports where projectID was already available.

  1. Fix broken MapSwipe stats on Partner Pages
    Partner Pages now correctly fetch and display MapSwipe statistics.
    The update prevents blocking behavior, handles CSRF authentication, and aligns the GraphQL query with recent MapSwipe changes—restoring accurate partner-level insights.
Expand to see detailed codebase changes 🖥️

Full Changelog: v5.2.1...v5.3.1

v5.2.1

15 Oct 13:41
aef1486

Choose a tag to compare

What's Changed

  • private project mapping and validation permission checks team membership along with project allowed users by @prabinoid in #7049
  • Hotfix: private project mapping and validation permission checks team membership along with project allowed users by @nischalstha9 in #7050

Full Changelog: v5.2.0...v5.2.1

v5.2.0

15 Oct 05:22
cda4fe1

Choose a tag to compare

Introducing Super Mappers and Badges

This release introduces two major new features:

  • Badges and
  • the new Super Mapper level, to better recognize mapper expertise and enhance project quality.

🏅 Badges

Badges are a brand-new way to celebrate mapper achievements. They’re automatically awarded based on your lifetime mapping activity in OpenStreetMap.

Examples include:
- 🛣️ Highways Badge: 1,000 km of highways created
- 🌊 Waterways Badge: 1,000 km of waterways created
- 🏠 Buildings Badge: 100,000 buildings created

Badges will appear on your Tasking Manager profile and Contributions page: https://tasks.hotosm.org/contributions

💪 Super Mapper Level

A new top-tier level, Super Mapper, sits above Advanced users.
To qualify, you’ll need to:
1. Earn the required badges (Highways, Waterways, Buildings)
2. Pass a human review by Tasking Manager admins (and later, select Super Mappers)

This new level helps project creators confidently assign complex mapping tasks to the most skilled contributors, thereby improving mapping quality and easing pressure on validator teams.

⚙️ Project Permissions

Project creators can now:
- Restrict mapping and validation access by mapper level, including the new Super Mapper level
- Restrict projects to Advanced-only users (previously unavailable)

Existing project permissions will automatically align with this new structure without changes.

This feature was made possible through a collaboration between HOTOSM and Codeando México with the idea proposed by @RAytoun. Please check out @SColchester's OSM diary post for further details.

Expand to see detailed codebase changes 🖥️

New Contributors

Full Changelog: v5.1.2...v5.2.0

v5.1.2

19 Aug 14:21
31551fe

Choose a tag to compare

What's Changed

Full Changelog: v5.1.1...v5.1.2