9 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Anonymous commented  ·  February 7, 2012 3:39 p.m.  ·  Delete

  I second the idea of having comments on all items, thus also on other comments. It's a must have feature. Otherwise it's pretty difficult to read and respond the 'chat-stream'.

• Jesse commented  ·  February 4, 2012 9:45 a.m.  ·  Delete

  I agree with the idea of having comments on all comments. The same info could be represented either in timeline mode (the default) or in threaded mode by expanding the comments for a given item as one does in the influx.

  The duality of each comment as both threaded and timelined would be very useful.

• Antti Vähäkotamäki commented  ·  April 5, 2011 6:08 a.m.  ·  Delete

  After thinking for this over the night I feel a good option would be to add a special "Import to influx" -action for each comment and file (unless they are already associated with an influx-item). The way attached influx is currently shown for a comment should work for this as well GUI-wise.

  The influx item would be generated automatically from the comment or file information. On the chat side the original comment would be attached to the created influx item but would be hidden from the discussion below the influx item.

  I think a natural addition among this would be to also allow uploading files as comments to influx items.

  These would in my opinion bridge the apparent problems people are currently having while trying to give structure to their discussions. The additional interface clutter would be minimal and the would still stay the same as it was before.

  I think this would open up many new use cases for Flowdock that were previously too cumbersome, but match actual needs for existing process flows (like the one Antonio Salazar Cardozo described below).

• Antti Vähäkotamäki commented  ·  April 4, 2011 2:03 p.m.  ·  Delete

  I feel the disconnect of functionality here coming from Yammer where every message can be responded to and they form a simple one level threads based on the bottom message (which wasn't a reply to anything). This is a discussion metaphor which seems to work very nicely.

  Just an idea from the top of my head (as a very inexperienced Flowdock user so please shoot me down if this doesn't work for some reason):

  Add all the chat messages that are not comments to influx items automatically as influx items of their own. Do the same for uploaded files.

  Where the influx comments now have a link to their influx item, you could add a more subtle "show in influx" -link to these comments and files which would make it easy to start a discussion based on them. This might also be called "Reply" ;)

  I know this would pollute influx a lot but I think this would be bearable given the filtering options you have there already. For those who want the old behavior quickly you could have a separate "All but chat items" selection in influx - which might even be the default view.

• Antonio Salazar Cardozo commented  ·  March 16, 2011 10:41 a.m.  ·  Delete

  FYI, the way we have dealt with this for now is that things that need comments (e.g., designs and issues/bugs) are emailed into the flow. It introduces a slight disconnect, but email offers a better way to compose those same messages much of the time, as well. Since you can comment on emails, it works out perfectly.

• nippr commented  ·  September 26, 2010 6:20 a.m.  ·  Delete

  I second the option of being able to comment on *everything*. It seems you guys have chosen to avoid the "threading" in the chat stream and go with tags instead. I am sure you have a logical reason for doing this - and I think it could help greatly with adopting (or moving along), if you wrote something about this in the "Tour" e.g. "At flowdock we have gone with the mindset of tags instead of threads because it adds these benefits...". Look forward to it! :-)

• Chris Raethke commented  ·  June 30, 2010 10:06 a.m.  ·  Delete

  +1 for comments on ALL FLOW ITEMS.

  I want to use it to track/share software issues, using tags for task type #task #bug, for priority #high #low then use the at @tom to assign issues

• jkgibbs commented  ·  April 8, 2010 2:20 p.m.  ·  Delete

  and be allowed to upload files in a comment as well

• rap1ds commented  ·  March 12, 2010 4:11 a.m.  ·  Delete

  As Antti said, it works now very nicely on influx items. So why not also on ALL FLOW ITEMS?

  Would be great if I could comment also on a simple flow message. For example if my friend is asking a question I could reply to that with a comment the same way I can do in Facebook feed (or Google Wave) for example.