Can a "resolved_at" date be exptrapolated via the last_updated_at on a discussion when reading via API

Zack Chandler's Avatar

Zack Chandler

21 Dec, 2009 06:07 PM

It would be great to have a resolved_at attribute on the discussion level.

Being as how there is none at the moment can the last_updated_at date serve as a "poor-mans" proxy for this field?

  1. 1 Posted by rick on 21 Dec, 2009 06:20 PM

    rick's Avatar

    Sure, we can add something though. Each comment has a boolean resolution attribute. resolved_at would just be the created_at timestamp of the latest comment to have a resolution.

  2. 2 Posted by Zack Chandler on 21 Dec, 2009 06:28 PM

    Zack Chandler's Avatar

    Ok, but instead of walking the comment tree couldn't you just assume that if the discussion state was equal to resolved, the last_updated_at probably contained the resolution? That is to say to new comments "touch" the last_updated_at timestamp on the discussion level?

  3. 3 Posted by rick on 21 Dec, 2009 06:50 PM

    rick's Avatar

    Perhaps, but you can also comment on resolved discussions.

    But yes, last_updated_at is the timestamp of the most recent comment.

  4. 4 Posted by Zack Chandler on 21 Dec, 2009 07:04 PM

    Zack Chandler's Avatar

    Thanks!

Discussions are closed to public comments.
If you need help with Tender please start a new discussion.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac