Support
Email-only, 1–2 business days.
Write to gitea-jira@wsagency.io. We do not offer in-app chat or phone support for this product.
Self-service
Check these before you write
-
1
Gitea is reachable over public HTTPS
Forge must call your Gitea API. A VPN-only or HTTP-only instance will fail connection and webhooks.
-
2
OAuth redirect URI matches
The Gitea OAuth2 application must use the exact redirect URI shown in the app settings. It changes if you reinstall.
-
3
Webhook deliveries
On a linked repository, open recent webhook deliveries. A failed HMAC or a 4xx from Forge usually means the secret or URL was edited on Gitea after linking.
Contact
How to reach us
Publisher
WEB rješenja d.o.o.Markuševečka cesta 115
HR-10000 Zagreb, Croatia
When you write
Include this so we can act
- Jira Cloud site hostname (example:
acme.atlassian.net) - Approximate time of the failure (timezone)
- Whether OAuth, repo linking, webhooks, or the issue panel failed
- Gitea version, and whether it is reachable from the public internet
- Webhook delivery status from Gitea, without secrets or tokens
Do not send OAuth client secrets, access tokens, or webhook HMAC secrets.