The system is great as is, but custom fields would take it to the next level as far as customizing information to suit the organization. Adding custom fields of different types (list, text, number, date, etc.) to the idea would help increase the flexibility.
Properties of the custom fields might include: * Whether the custom field is required * Who can see the custom field (moderators or everyone) * Type of custom field * Default value of custom field
I think the right way here would be to integrate with QuestionPro (Survey Tool) -- it would require significant re-engineering but would achieve the most flexibility.
I'm not sure a survey tool is the right direction or not. I'm thinking more along the lines of making it flexible enough to turn into a software development tool (i.e. - issue tracker type software). That is why I was wanting the custom fields...mostly for internal development fields.
I'm not familiar with that tool, but the key for us would be that we can use such fields to maintain automated integration with our tools and processes. Links back to other system could be stored in Custom Fields, and state variables could be attached to keep track of work flow.
We're very excited that this feature has been added. We can see from the documentation that you already know that editing, exporting (and importing) of Custom Field values will be key to successful use of Custom Fields.
I would add that access to the history of those values and auditability of when the values change and who changed them, etc. will also be important.
My ideascale tracks different development ideas for our software product. Users know we can only work on so many things and have no idea how much effort some of the ideas would require. It would be helpful to have a custom field that we could put "Development Effort" info into.
Revise
Vote Up
Vote Down
Post New Comment
Close