jeff.holek
My feedback
-
13 votesjeff.holek
supported this idea
·
-
43 votesjeff.holek
supported this idea
·
-
80 votesjeff.holek
supported this idea
·
-
275 votes
Carter Gibson
responded
jeff.holek
supported this idea
·
-
63 votes
An error occurred while saving the comment jeff.holek
supported this idea
·
-
391 votes
Hi – we have spent time investigating this and talking with many of you, and have decided to defer from building this for the time being. In our conversations with customers, we came across many different use-cases for custom fields and think we could potentially provide better, native support for some of the common use-cases like “priority” or “impact” rather than attempting to solve several problems with this one feature. We may revisit this idea after providing out-of-box support for the most common use cases.
An error occurred while saving the comment jeff.holek
commented
Given the volume of interest, and extended timeline before a decision (7 years), which was more of a delay than a resolution, could we please get some feedback regarding expectations for these three features?
Are we starting from scratch?
What still remains before your team reviews this for development feasibility?
There were 300+ users supporting this, and now across all 3 we have about 20 each. These 3 topics have lost their momentum due to this split.
jeff.holek
supported this idea
·
Given the volume of interest, and extended timeline before a decision (7 years), which was more of a delay than a resolution, could we please get some feedback regarding expectations for these three features?
Are we starting from scratch?
What still remains before your team reviews this for development feasibility?
There were 300+ users supporting this, and now across all 3 we have about 20 each. These 3 topics have lost their momentum due to this split.