Notifications
Clear all

[Sticky] How to Report Issues & Request Features!!!

1 Posts
1 Users
0 Reactions
5 Views
Talantly Ai
(@talantly_ai)
Posts: 8
Talantly Ai Admin
Topic starter
 

🐛 Reporting Issues

Before You Post

  • Search first - Check if someone has already reported the same issue
  • Try basic troubleshooting - Refresh the page, clear browser cache, or try a different browser
  • Check browser compatibility - Ensure you're using a supported browser

Issue Report Template

Use this format for bug reports:

Title: Brief, descriptive summary (e.g., "Login fails with Google authentication")

Description:

  • What happened: Describe the actual behavior
  • What you expected: Describe what should have happened
  • Steps to reproduce: List exact steps to recreate the issue
    1. Open the app
    2. Tap "Login with Google"
    3. Select account
    4. App crashes

Additional Details:

  • Browser: (Chrome 120, Firefox 121, Safari 17, etc.)
  • Operating System: (Windows 11, macOS 14, Ubuntu 22.04, etc.)
  • Device Type: (Desktop, laptop, tablet, mobile)
  • Screen Resolution: (if layout-related issue)
  • Browser Console Errors: (Press F12 > Console tab, copy any red errors)
  • Screenshots/Videos: Include if helpful
  • Error messages: Copy exact text if any

Priority Guidelines

  • Critical: App crashes, data loss, security issues
  • High: Core features broken, significant usability problems
  • Medium: Minor bugs, cosmetic issues
  • Low: Enhancement suggestions, nice-to-have fixes

✨ Requesting Features

Before You Post

  • Search existing requests - Your idea might already be suggested
  • Consider the audience - Will this benefit most users?
  • Think about alternatives - Are there existing workarounds?

Feature Request Template

Use this format for feature requests:

Title: Clear, concise feature name (e.g., "Dark mode support")

Problem Statement:

  • What problem does this solve?
  • Who would benefit from this feature?
  • How does the current app fall short?

Proposed Solution:

  • Describe your ideal implementation
  • Include mockups, sketches, or examples if possible
  • Consider different user scenarios

Alternatives Considered:

  • What other solutions did you think about?
  • Why is your proposal the best approach?

Additional Context:

  • Similar features in other apps
  • User research or feedback supporting this
  • Technical considerations you're aware of

📝 General Forum Guidelines

Writing Effective Posts

  • Use clear, descriptive titles - Avoid "Help!", "Bug!", or "Feature request"
  • Be specific and detailed - More information is better than less
  • Use proper formatting - Use bullet points, numbered lists, and headers
  • Include relevant tags - Help others find and categorize your post
  • Be respectful and patient - Our team and community volunteers help when they can

What NOT to Do

  • ❌ Post duplicate issues without checking existing posts
  • ❌ Bump old posts repeatedly - comment only with new information
  • ❌ Post in wrong categories (use "Issues" for bugs, "Feature Requests" for suggestions)
  • ❌ Include personal information, passwords, or sensitive data in screenshots or console logs
  • ❌ Use ALL CAPS or excessive punctuation!!!!!
  • ❌ Post off-topic content or spam
  • ❌ Share account credentials or API keys

Response Expectations

  • Issues: We aim to acknowledge within 2-3 business days
  • Feature Requests: We review monthly and update status quarterly
  • Updates: You'll be notified when status changes or we need more info
  • Resolution: We'll mark issues as "Fixed" when released and close duplicate/invalid reports

Getting Help Faster

  1. Follow the templates - Complete reports get faster attention
  2. Include browser console logs - Technical details help our developers debug
  3. Test in different browsers - Helps identify browser-specific issues
  4. Be available - Respond promptly if we ask for clarification
  5. Test fixes - Help verify when we deploy potential solutions
  6. Vote on existing posts - Use reactions to show support for features/issues

🏷️ Post Categories & Tags

Categories

  • 🐛 Issues - Bug reports and technical problems
  • ✨ Feature Requests - New functionality suggestions
  • ❓ Questions - General help and usage questions
  • 💡 Ideas - Brainstorming and discussion

Common Tags

  • chrome, firefox, safari, edge - Browser-specific
  • desktop, mobile, tablet - Device type
  • login, dashboard, notifications, reports - Feature areas
  • critical, high, low - Priority levels
  • confirmed, investigating, planned - Status updates

🤝 Community Guidelines

Be constructive: Focus on solutions and improvements, not just complaints.

Search before posting: Avoid duplicate posts by checking existing discussions.

Stay on topic: Keep discussions relevant to the original post.

Help others: If you know the answer to someone's question, share your knowledge.

Follow up: Update your posts if you find solutions or workarounds.

Remember: This forum is a collaborative space where users and developers work together to improve the app. Your detailed reports and thoughtful suggestions help make the app better for everyone!

 
 
Posted : 16/07/2025 11:06 am