Feature Request vs Improvement Request

[JonL]

@George

How do you guys handle big feature requests vs improvement requests(small iterations).

I am assuming you monitor the feature request category and pay more attention to those topics that have a lot of votes or a hot.

However I don’t know how you handle small iterations for existing features.

I just added two new FR but they are actually small iterations and will never get high visibility in terms of votes like adding a calendar.

But I’m pretty certain they are reasonable requests that won’t take much effort. I know that for the great majority of users they might not find them useful although they are in certain contexts. At least for power users.

AC Flows -> New action: Wait for callback

Given that now we can call javascript it would be great to have an action in flows that just waits for a callback to continue with the next steps. So basically the async/promise and await workflow. Right now if we call a javascript there is no easy way to return to the flow that initiated the call. I am thinking of adding the wait for callback step and we get automatically a piece of code to copy and paste in our callback function et voila the flow continues where it was waiting.

and

Server Connect Response Action -> Set Content-Type in response headers

Could we have an option to write in a field the Content-Type for the response headers? Right now it just provides the charset. Although not as critical as in the request it’s important when providing user access to consume our own API.

[George]

Well we don’t have a specific flow in handling small requests. You just have to “promote” them more so we see that their are really easy and implement them quickly