Improvements for the Idea area of the Community

By Curt Raddatz on 21 Mar 2014
A list of possible enhancements.  I searched in the ideas area to see if these were already there and couldn't find anything.  If this should be merged with something else, please do so.

Minor Enhancements

• View sequence – in addition to most recent and most liked, add all the ‘marks’ (see below) which will allow me to see the ideas that are currently being worked on or not worked on.

• Idea numbers – assign numbers that are viewable everywhere the heading is viewable.  When there are hundreds or thousands of ideas, many with similar headings, using a number will help identify the correct idea when being discussed.

Enhancements to the 'Status' of an Idea (modeled after information found here - http://www.outsystems.com/forums/discussion/11570/user-stories-for-woc/)

• Marking an idea as “planned implementation”

As a manager a user will be able to add mark an idea as ‘planned implementation’. In doing so, the manager shall set an expected delivery date and release version and add a comment. The expected delivery date and version is visible to collaborators.

• Marking an idea as “implementation in progress”

As a manager a user will be able to add mark an idea as ‘planned implementation’. In doing so, the manager shall set an expected delivery date and release version and add a comment. The expected delivery date and version is visible to collaborators.

• Marking an idea as “tentative implementation”

As a manager a user will be able to add mark an idea as ‘tentative implementation’. In doing so, the manager shall set a tentative delivery date and release version and add a comment. The expected delivery date and version is visible to collaborators.

• Marking an idea as “rescheduled implementation”

As a manager a user will be able to add mark an idea as ‘tentative implementation’. In doing so, the manager shall set an expected delivery date and release version and add a comment. The expected delivery date and version is visible to collaborators.

• Marking an idea as “not planned for implementation”

As a manager a user will be able to add mark an idea as ‘not planned for implementation’. In doing so, the manager shall add a comment indicating why the idea is not planned (no resources, needs research, etc.).

• Marking an idea as “not feasible for implementation”

As a manager a user will be able to add mark an idea as ‘not planned for implementation’. In doing so, the manager shall add a comment indicating why the idea is not feasible (too much effort, viable workaround, etc.).

• Marking an idea as “no longer needed”

As a manager a user will be able to add mark an idea as ‘no longer needed’. In doing so, the manager shall add a comment indicating why the idea is no longer needed.  For example, there are many ideas for Outsystems that are changes to Enterprise Manager, a component that no longer exists.

• Marking an idea as “implemented”

As a manager a user will be able to add mark an idea as implemented with a completed date and version number.


Rationale for these improvements

• Provide a roadmap for people – what are the plans going forward – will my favourite idea be implemented soon or do I need to implement that myself.  For example, the most voted on idea has been around since May 2010.  I have no idea if anyone is working on it or if it’s even possible.  How can this be?  Whoever manages the ideas should be able to provide users information about every idea and where it is (or isn’t) in the pipeline.  So knowing a release timeline and what ideas are at least tentatively planned would be a huge help.

• Work in Progress – currently shows the major release but what happens when it feature misses the target release (there are a few examples out there)?  Should be changed to ‘rescheduled implementation’.

Justin James22 Mar 2014
From *my* perspective, these improvements would be great. But I know that OutSystems historically likes to keep a lot of the information regarding what is under development pretty quiet, so I really doubt that we will see these changes.

J.Ja
J.24 Mar 2014
What JJ said basically.


Curt Raddatz24 Mar 2014
JJ, I kind of knew that based on our discussions in the past.  I certainly wouldn't want Outsystems to give away any big secrets or commit to something they couldn't deliver.  It would be a shame though if someone took a bunch of time to develop a feature because they really needed it only to find out when the next release comes out that Outsystems already did it.  If Outsystems looked at it and said either (a) they had no plans for it or (b) it's in progress with a tentative release date or (c) it's tentatively planned for release x that would be a huge benefit to the community.  It might benefit them as well.  For example, you just created that Trig extension because you needed it and Outsystems had no plans for that.  Now they can incorporate your extension (like they've done with other components) and improve the product at almost no cost.