Request features and report issues

Help includes support actions for product feedback and issue reports. Use these actions when a help article does not solve the problem, a process needs improvement, or the app behaves differently than expected.

Use support actions when you need to:

1. Ask for a new feature or product improvement.
2. Report a bug or broken process.
3. Explain a missing or confusing help article.
4. Share context from the page where the problem happened.
5. Send details that help the team reproduce or evaluate the request.

Terms you may see:

• Ask for new feature is for improvements, missing capabilities, and process ideas.
• Report an issue is for bugs, errors, broken UI, incorrect data, or unexpected behavior.
• Feedback dialog collects the category, subject, and supporting details.
• Current page context can be included automatically so the team knows where you were working.

Before you start

• Help must be available from the app header or account menu.
• Network access is required to submit feedback.
• Do not include passwords, payment card numbers, private keys, or sensitive secrets in the message.

How app navigation works

1. Open Help.
2. Go to Need more help?.
3. Choose Ask for new feature or Report an issue.
4. Complete the feedback dialog.
5. Submit the request.

Expected outcome: The request is sent with enough context for the team to review it.

Ask for a new feature

1. Open Help from the app header or account menu.
2. Go to Need more help?.
3. Select Ask for new feature.
4. Add a short subject.
5. Explain the outcome you need, who needs it, and why the current process is not enough.
6. Submit the request.

Good feature requests include:

• The job you are trying to complete.
• The current workaround, if any.
• Who is affected.
• How often the need occurs.
• What a successful improvement would let you do.

Report an issue

1. Open Help from the page where the issue happened when possible.
2. Go to Need more help?.
3. Select Report an issue.
4. Add a short subject.
5. Describe what you expected, what happened, and how to reproduce it.
6. Submit the report.

Good issue reports include:

• The Space, page, item, or process where it happened.
• The exact action you took before the issue appeared.
• What you expected to happen.
• What actually happened.
• Whether the issue repeats after refresh.
• The approximate time of the issue.

Report missing help content

1. Search Help first.
2. If no article matches, select Report an issue or Ask for new feature depending on the need.
3. Include the terms you searched for.
4. Explain what article, guide, or process help you expected.

Troubleshooting

Feedback does not submit

• Symptom: The submit action fails or nothing happens.
• Cause: The app may be offline, the required fields may be missing, or the request failed to save.
• Resolution:
  1. Confirm the subject and details are filled in.
  2. Confirm you are online.
  3. Try again after a short wait.
  4. If the issue is urgent, use your organization’s support escalation path if one is available.

You are not sure whether to request a feature or report an issue

• Symptom: You know something is wrong, but not whether it is a bug or enhancement.
• Cause: Some process gaps can look like product bugs.
• Resolution:
  1. Use Report an issue when something previously worked, errors, or behaves incorrectly.
  2. Use Ask for new feature when the app works as designed but does not support the process you need.
  3. Include enough detail so the team can reclassify it if needed.

You need urgent help

• Symptom: The issue blocks critical work, security, billing, or data recovery.
• Cause: Help feedback may not be the fastest emergency channel for every organization.
• Resolution:
  1. Submit the issue with clear urgency and impact.
  2. Also use your organization’s direct support, admin, or escalation channel if available.
  3. Avoid repeatedly submitting duplicate reports for the same incident.

FAQ

Should I search Help before sending feedback?

Yes. Search first when you need product guidance. Send feedback when the article is missing, unclear, or the product behaves unexpectedly.

Can support see where I was in the app?

The app can include current page context with the request. Still include the item name, Space, and action steps when they matter.

Should I include screenshots?

If the feedback dialog supports attachments in your version, include a screenshot when it helps explain layout, error messages, or unexpected state. If attachments are not available, describe the screen clearly.