Reference
Troubleshooting
Find the symptom, then the fix. Still stuck? Email support@yti.digital.
Scenarios panel
| Symptom | Fix |
|---|---|
| The panel is missing on an issue | An administrator chooses ••• → Show for all work items on the panel once. See Install and set up. |
| There is no Edit button | You need the Edit issues permission on this issue, or the licence is not active. |
| Save is disabled | The text has a Gherkin error; the message above the editor says which line. |
| "Someone saved a newer version" | Your text is still in the editor. Copy your changes, reload, apply them and save. |
Connecting Git
| Message | Fix |
|---|---|
| "… rejected the token" | The token is wrong or expired. Create a new one and save it. |
| "Repository or branch not found" | Check owner, repository and branch spelling, and that the token can see this repository. |
| "The token has no access to this repository" | Give the token access to the repository (GitHub: repository access; GitLab: Maintainer; Bitbucket: token created in this repository). |
| URL and secret shown after saving | The token can't create webhooks. Add the webhook by hand, see the guide for GitHub, GitLab or Bitbucket. |
Sync
| Symptom | Fix |
|---|---|
| A push doesn't update Jira | Check that the push went to the configured branch, the file is inside the folder and has the issue key in its name or an @KEY tag. In the Git host, the webhook's recent deliveries should show success. |
| A save doesn't reach Git | The panel shows the reason. If the token expired, save a new one in the settings. |
| "Not in sync with Git" | Both sides changed. Choose a version, see How sync works. |
CI uploads
| Response | Meaning and fix |
|---|---|
401 | Missing or wrong X-API-KEY. Use the current key; a new key replaces the old one. |
404 | No upload key exists yet. Create one in the settings. |
400 | The body is not a Cucumber JSON report. Upload the file with --data-binary. |
402 | The FeatureBridge licence for the site is not active. |
202 | Accepted. If results don't appear, the features need an @KEY tag or the key in the file name. |
Something else? Email support@yti.digital with the issue key and what you see.