Forums » SECloud Feature Requests

Submitting Feature Requests

This topic has been closed.
    • 4239 posts
    June 21, 2017 12:47 PM EDT
    SocialEngine Cloud and want to get involved? Thanks! There are plenty of ways you can help!

    Please take a moment to review this document in order to make the contribution process easy and effective for everyone involved.

    Following these guidelines helps to communicate that you respect the time of the developers managing and developing this project. In return, they should reciprocate that respect in addressing your feature requests.

    Using the feature request tracker

    The feature request section is the preferred channel for feature requests but please respect the following restrictions:

    * Please do not use the feature request tracker for personal support requests. If you need support, please post in the relevant forum area or submit a ticket to our support via your client account.

    * Please do not derail or troll issues. Keep the discussion on topic and respect the opinions of others.

    Feature requests
    A feature is a new function that is implemented in SocialEngine Cloud.

    Feature requests are welcome, but take a moment to find out whether your idea fits within the scope and aims of SocialEngine. It's up to you to make a strong case to convince the SocialEngine developers of the merits of this feature. Please provide as much detail and context as possible.

    A good feature helps a multitude of people with the least negative impacts on the SocialEngine script.

    Guidelines for feature requests:

    1. Use the Forum search — check if the feature has already been requested.

    2. Check if the feature has been added — double check for the feature in the latest cloud release notes.

    3. Fully describe the feature — Give detailed descriptions of what this feature does. Ideally, create screenshots so we can visually see what you are requesting when possible.

    4. One request per issue — for better clarity, include only one feature per issue opened.

    A good feature request shouldn't leave others needing to chase you up for more information. Please try to be as detailed as possible in your request. What area is this for (activity RSS Importer, mail, theme, etc)? What do you wish to achieve with this feature? What are the benefits? Why should we consider adding this feature? Does this feature require specific settings?


    Short and descriptive example feature request title

    A summary of the feature request.

    Details of settings, steps to use or see this feature, benefits.

    Add screenshots when possible.

    Any other information you want to share that is relevant to the feature being requested. This might include the lines of code that you have identified as needing improvements and potential solutions (and your opinions on their merits).

    Here's a sample of a feature request:

    Title: Integrations - Add Wordpress

    Description: It would be great to add a Wordpress integration so we can connect to our wordpress blog or blogs.

    This request would allow us to add a blog function via wordpress to our Cloud sites.

    (This is where we would see a screenshot for the feature)

    This would benefit a great deal of clients as they could add their personal blogs, business blogs or other blogs they want to integrate with.

    Thanks for considering my request!

    We reserve the right to remove, edit or alter any comments or feature requests or block anyone from posting to our tracker should they violate these terms.