To help us understand your needs and design the right solution, follow these guidelines when submitting a new feature or change request.

 

1. Write a clear title

Use a short title or subject line that explains the request in simple terms.

Good examples:

✅ “Add bulk edit option for metadata fields”

✅ “Extend email notifications for new uploads”

Avoid titles like:

❌ “New feature”

❌ “Improvement”

❌ “Can we change this?”

 

2. Explain the goal

Describe what you want to achieve and why. Focus on the problem or business need, not just the solution.

This is the most important step.

Example:

  • “We need a way to group assets more efficiently to reduce manual selection time when sending recommendations.”

 

3. Describe a proposed solution

If you already have a solution in mind, let us know!

Example:

  • “It could be a ‘save as preset’ option for asset selections.”

 

4. Provide a use case

Explain how and when this would be used in real life.

Include:

  • Who would use it?
  • In what workflow?
  • How often?

 

5. Include examples or references

Visual examples are extremely helpful.

If possible, include:

  • Screenshots
  • Sketches or mockups
  • aLinks to similar features elsewhere

 

6. Describe the expected outcome

What would success look like?

Example:

  • “Users should be able to reuse a saved asset selection without reselecting items manually.”a

 

7. Set a priority

If something is urgent, please indicate:

  • Low / Medium / High
    How critical is the feature or change?
  • Business impact
    Briefly explain why it’s time-sensitive

 

8. One topic per ticket

Keep each ticket focused on a single request — it keeps things clear and easier to estimate.

 

 

Did this resolve your query? Contact support@mediafellows.com for further help.