Hi all,
Reading through the product ideas raised by the community - it strikes me that there are significant clusters. Two jump out - improvements to date/time handling & parsing, and caching.
This is not a suggestion about either of these topics, but a question about how we look at and structure these ideas. Let's take the date-time ones (full list is below) as a worked example:
- there are 23 distinct ideas (or 22 if you exclude the one about generating random dates) which relate to the treatment (mainly parsing; formatting or constructing) of dates & times
- None of these individually has enough votes to get them onto the "hot ideas" list - however when you look in aggregate across them, the theme of "standardizing and enriching date-time processing" is probably one of the hottest topics at the moment.
Two suggestions:
Tagging: If we are able to spot these patterns - and then create a tag that is related to this (in this case "DateTime handling") - the product team would probably be able to do some pretty interesting analytics.
Grouping: In order to allow people to spot these BEFORE they log the next idea which is trying to achieve the same thing - is it worth the community creating a grouped-up idea which then becomes persistent if there is a clear trend; and we can link out to these ideas? For example an idea saying "standardize & Enrich treatment of date time", which then becomes a sticky item at the top of the forum so that folks don't have to search for pages to see if their idea is a duplicate.
NOTE: this second one (grouping) will also save time for the product team because they won't have to spend as much time flagging duplicates...
Hope this makes sense - as always, happy to help in thinking about potential solutions.
Note: the 23 ideas related to date-time treatment are captured below (as a worked example), and the authors of these ideas have been tagged out of courtesy
@DultonM @braxtone @Philip @AshokBhatt @CSchrader @dawid_nawrot @jdunkerley79 @Joe_Lipski @ChadB @nicholas_carstens @GGuenther @AndrewW @RachelW
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.