nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

I want to activate ProForma Forms for a single project, but the only interface lists 50 projects

Craig Duffy_aoricj

Hi, I want to activate ProForma Forms for a single project, but the only interface lists 50 projects at a time. We have "on by default" deactivated, so its not universally available; admins need to turn it on for a project on a case by case basis. We have over 1800 projects, so scrolling through those projects as a Jira Admin is going to take a LONG time, just so that I can activate it for a single project. Is there an easier way?

Accepted answers

Germán Morales

Hi @Craig Duffy , checked the Forms REST API and there's no endpoint to flip the feature on for a project, it only covers form templates once Forms is already enabled there. The global toggle screen you're paginating through has no scriptable equivalent today.

The official admin guide for that screen documents exactly two actions: toggle a single project, or a bulk toggle that turns Forms on for every project at once. Nothing for a filtered subset or a search box.
Since there's no self-service way around the pagination, this is worth raising with Atlassian Support directly as a product gap for large sites, not just a one-off question, 1800 projects at 50 per page is a real usability problem.
As a stopgap, if that list happens to be sorted alphabetically or by key, jumping straight to the page matching your project's first letter will save you most of the scrolling versus starting from page one.

All comments

Germán Morales

The official admin guide for that screen documents exactly two actions: toggle a single project, or a bulk toggle that turns Forms on for every project at once. Nothing for a filtered subset or a search box.
Since there's no self-service way around the pagination, this is worth raising with Atlassian Support directly as a product gap for large sites, not just a one-off question, 1800 projects at 50 per page is a real usability problem.
As a stopgap, if that list happens to be sorted alphabetically or by key, jumping straight to the page matching your project's first letter will save you most of the scrolling versus starting from page one.