• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

kobotoolbox / kpi / 44286489618
86%
master: 76%

Build:
Build:
LAST BUILD BRANCH: release/2.026.43
DEFAULT BRANCH: master
Ran 18 Nov 2026 10:38AM UTC
Jobs 10
Files 892
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

18 Nov 2026 10:33AM UTC coverage: 86.052%. Remained the same
44286489618

push

github

web-flow
fix(library): allow publishing collections when sector field is disabled DEV-3214 (#7876)

### đŸ“Ŗ Summary

Collections can be made public again on servers that don't use the
sector field.

### 📖 Description

On a server where the sector field has been removed from the project
metadata, a collection has no way to get a sector. **Make public** still
asked for one, so it always failed with "Name, organization and sector
are required to make collection public." Publishing now only asks for a
sector when the server offers that field. Servers that keep the sector
field behave as before.

### 💭 Notes

- Frontend only. The check lives in `isAssetPublicReady`
(`jsapp/js/assetUtils.ts`); the backend has no publish validation.
- The check now reads the same `project_metadata_fields` config that
`LibraryAssetForm` uses to decide whether to show the sector select.
- When sector isn't offered, the error message drops it: "Name and
organization are required to make collection public." This is a new
translatable string.
- I kept sector required whenever the field is offered, even if the
config marks it `required: False` (the default). Tying publishing to the
`required` flag would change default servers, which this ticket doesn't
ask for.

### 👀 Preview steps

1. â„šī¸ on Main as a superuser, plus a regular account. In
`/admin/constance/config/`, remove the `sector` entry from
`PROJECT_METADATA_FIELDS` and save (put it back when done)
2. as the regular account, go to `#/library/my-library`, click **NEW** >
**Collection**, fill **Name** and **Organization** (there is no sector
field), click **Create**
3. inside the collection, click **NEW** > **Template**, give it a name,
click **Create**, then go back to the collection (it should show 1 item)
4. click **Make public**
5. 🔴 [on main] an error says "Name, organization and sector are required
to make collection public." and the button stays **Make public**
6. đŸŸĸ [on PR] no error, the button changes to **Make private**
7. đŸŸĸ als... (continued)

10971 of 13782 branches covered (79.6%)

34316 of 39878 relevant lines covered (86.05%)

5.82 hits per line

Jobs
ID Job ID Ran Files Coverage
1 44286489618.1 18 Nov 2026 10:38AM UTC 887
54.48
2 44286489618.2 18 Nov 2026 10:43AM UTC 892
69.09
3 44286489618.3 18 Nov 2026 10:44AM UTC 889
60.64
4 44286489618.4 18 Nov 2026 10:58AM UTC 887
57.42
5 44286489618.5 18 Nov 2026 10:58AM UTC 890
66.58
6 44286489618.6 18 Nov 2026 10:59AM UTC 889
55.81
7 44286489618.7 18 Nov 2026 11:02AM UTC 889
51.42
8 44286489618.8 18 Nov 2026 11:02AM UTC 887
50.06
9 44286489618.9 18 Nov 2026 11:07AM UTC 887
59.47
10 44286489618.10 18 Nov 2026 11:10AM UTC 889
59.01
Source Files on build 44286489618
  • Tree
  • List 892
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • c3aaf1c6 on github
  • Prev Build on main (#44097547713)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc