Get Help

Not sure how to do something?

Community Support

Ask questions and get help from our active community on the GitHub Issues page.

Pro/Enterprise Support

Get faster response times with guaranteed SLA and direct help from our team with 4ga Boards Pro, Enterprise or Support Plans using our contact form or email.

Benefits:

• Faster response times with guaranteed SLA
• Direct contact with 4ga Boards support team
• Ability to share more private details, whole support chat is never shared publicly
• Multiple support options available: technical, implementation in the company, issues, data imports, feature requests, training, onboarding

Report a Bug

Something not working as expected?

How to Report an Issue?

For bug reports please use our GitHub Issues page (preferred), contact form or email.

How to Report Security Issue?

Please use GitHub Private Vulnerability Reporting page (preferred), contact form or email for security related issues.

Do NOT create public issues on GitHub for security vulnerabilities.

Guidelines

Before posting a bug report, please check if there is already existing one. When creating a bug report, please include as many details as possible.

Request New Features

4ga Boards missing some features?

Propose Code Changes

If you are familiar with our technology stack, you can propose code changes by opening a Pull Request on our GitHub page.

The easiest way to do it:

• Fork 4ga Boards repository
• Make some commits with changes
• Create new Pull Request
• Adapt your changes to reviewers feedback

Please check out our contribution guidelines here.

Describe New Feature

Describe the feature you want to see in 4ga Boards by opening an issue on our GitHub Issues page.

Pro/Enterprise Feature Request

Describe the feature you want to see in 4ga Boards by opening an issue on our GitHub Issues page (preferred), contact form or email.

When using GithHub Isses. please remember to let us know about your current 4ga Boards plan using email, so we can assign higher prority.

Benefits:

• Higher Feature Request Priority
• Ability to use your support hours on developing new feature by our team

Donate to Support Feature Development

Don't have 4ga Boards plan, but want to help develop new feature faster?

Donations temporary unavailable.

Code Contributions

Want to propose code changes to develop a new feature or fix a bug?

Propose Code Changes

If you are familiar with our technology stack, you can propose code changes by opening a Pull Request on our GitHub page.

The easiest way to do it:

• Fork 4ga Boards repository
• Make some commits with changes
• Create new Pull Request
• Adapt your changes to reviewers feedback

Contributing Guidelines

Thanks for taking the time to contribute!

If you're looking for ways to get started, here's a list of ways to help us improve 4ga Boards:

• Bugs and other issues listed on GitHub Issues page
• New features development
• Performance improvements, both on client and server
• Translations into other languages
• Documentation

You can discuss your ideas with the 4ga Boards team by creating an issue, commenting on an existing one or creating a Pull Request. This will result in a much higher likelihood of your code being accepted.

Git Commits Guidelines

Commit messages should follow the commit message convention, so changelogs could be automatically generated.

Additional rules:

• Capitalize the subject line
• Do not end the subject line with a period
• Use the body to explain what and why vs. how
• Each commit should be a single, stable change

All JavaScript code should follow this JavaScript style guide. The pre-commit hook will help you find linting errors before committing.

Translations

Incomplete translations or missing language?

Submit Fixes or New Translations

To sumbit fixes to an existing translation or propose new translation, create a Pull Request on the GitHub Pull Requests page, or create new issue and upload translations there.

You can find translation files here.