Troubleshooting and FAQ

Troubleshooting & FAQ

Installation

composer install complains about the PHP version. Studio needs PHP 8.4. Check with php -v, and make sure the CLI and PHP-FPM use the same version.

The installer stops with a database error about pg_trgm. Create the extension in your database: CREATE EXTENSION pg_trgm; (as a superuser).

"The provided host name is not valid for this server." Add your host to $settings['trusted_host_patterns'] in settings.php.

The status report says QA evidence storage: Not configured. Add $settings['file_private_path'] = '../private/files'; to settings.php, create the folder, make it writable by PHP, and clear caches (drush cr).

Everyday use

I can't see a Development (or its artifacts, tests…). You need to be its owner, its responsible person or a member. Ask the responsible person to add you in the Development's Edit tab. See Users and roles.

I can't see a project, or its board is empty for me. You need to be its owner, manager or a member, or a member of one of its parent projects. Ask the project manager to add you.

I can't drop a card in a column. The move was refused: usually the stage isn't on that project's board, or you can't edit the task. The message on screen says which.

I'm a tester but I don't see some runs. Testers only see the runs assigned to them. Ask your QA lead to reassign the run or create one for you, or create your own from an active plan with New Test Run.

There's no Start Run button. Either the run has no executions (none of the plan's cases were Ready when it was created; a lead can mark them Ready and use Generate Executions), or you're not its tester or a lead.

I can't edit a result anymore. The run is completed, so its results are historical evidence. A QA Manager can reopen the run.

I clicked the wrong result. Use Correct Result and give a reason. It's recorded in the correction history.

Why can't I delete this run / test case / requirement? Because it holds history: a run with results, a test case that was executed, a record in a baseline. Cancel the run, mark the case obsolete or deprecate the requirement instead.

Readiness says something is missing but I want to move on. That's fine: readiness is advisory. Mark the milestone as reached, confirm, and what was missing is written in the milestone notes.

The overview says "The Development Case changed after it was applied". Someone edited the case. Your Development keeps its snapshot until you re-apply the case from the overview. Have a look at what changed first.

I added a trace and Studio refused it. Read the message: it's usually one of the trace rules, for example linking records of two Developments, or relating a test with something other than Verifies.

Can I import requirements from a spreadsheet? Not from the UI yet. Studio is Drupal, so the Migrate API, JSON:API or a small Drush script all work. Contributions welcome!

"The repository path is outside the allowed repository roots." Clone it below one of the roots in Configuration → Code Source (default /opt/repos), or add its folder to the roots.

Indexing says the ref "does not resolve to a commit". The ref must exist in the clone on the server. Run git fetch there, and use the exact name (main, origin/main, v1.2).

"No database is registered with the identifier …" The snapshot names a database Studio does not know. Register it in a Development with that identifier, or say which database to import into (--database=DB-0001, or ?database= over HTTP).

The import says "unchanged". The schema is the same as the latest snapshot, so Studio kept history clean. Add force if you really want a snapshot of it.

For administrators

How do I back up Studio? The database (drush sql:dump) plus the private files folder. That's all.

How do I update? git pull && composer install && drush updatedb -y && drush cr. See Installation.

Drupal shows "There is a security update available". Update core and contributed modules with Composer (composer update "drupal/core-*" --with-all-dependencies, then drush updatedb). Test on a copy first.

Something else? Open an issue with what you did, what you expected and what happened. Screenshots help a lot.