Navigate to Issue Tracking page in the above menu: Support > Issue Tracking
Then use the “Report an Issue” button and select “Wish”

Wish title:

The title of the wish report needs to be short, but specific enough to explain the issue.
Platform, Product, Module Code prefixes are used only if affecting a specific Platform, Product, or Module.
The title format is: Prefixes>>Short Description
Goal is to understand the wish idea/need from just reading the title and use that title in further communication and it's lifecycle.

Description:

Stick to format:

• - Current (mandatory)
• - Need (mandatory)
• - Wish (suggested design is not mandatory)

When documenting a New Wish it is important to be clear on what the Need is.
In essence, the need comes from the end user, as the user needs a system to help run their business in the most efficient, legal, productive and automated way. The wish therefore should explain if the need is:
- a legal requirement
- a productivity/efficiency/automation improvement

Do not mix the Need with a Solution/Design. The need is a "user story" of what the end result should provide. The Solution/Design is how the system will be programmed to achieve the need. You can suggest the solution/design, but you must clarify the need first.

Tags:

Don't forget to add Tags.
It helps filter and find this wish and related wishes by topic when planning development camps.

Attachments:

Make sure to attach:

• - screenshots for UI improvement wishes - current and sketch of what is needed
• - text backup - if certain setup steps must be done before testing/developing the functionality from wish
• - documents - API documentation, and other helpful documentation
• - links - if a reference to something is mentioned, or if an integration has public development documentation in swagger or some other tool

——
When the wish report is completed use the wish title when chatting a channel manager or development manager about it.

All wishes need to get approval.