2510c1e0ac
Major rework of the command/ai abstractions
...
- Big simplification of the overall workflow.
- Composite commands store their commands properly, these are undoable now.
- Child commands are excluded from history
2025-05-16 13:29:18 +02:00
67984bf589
WIP for LLM experiment
2025-05-16 13:29:18 +02:00
181e35b5b2
Restore command when clicking on it
2025-05-07 12:03:02 +02:00
cc039e0831
Add missing index to commands
2025-05-06 22:51:38 +02:00
9d7459f865
Show recent commands
2025-05-06 08:54:58 +02:00
65d809dd8d
Basic models for Fizzy do and searches working with them
2025-05-06 06:42:33 +02:00
2d2cd702ca
Remove summary id column too
2025-04-30 10:18:02 +02:00
174bb21b8a
Drop event summaries too
...
We'll regenerate with a script
2025-04-30 09:55:29 +02:00
2b98db9e66
Flatten out comments and messages
...
https://37s.fizzy.37signals.com/collections/693169850/cards/999008989#comment_994777841
2025-04-29 19:21:18 +02:00
e90b062440
Configure the autoclose period at the collection level
2025-04-25 13:29:16 +02:00
6a1dcef6ef
Add script to migrate existing events to the new format
2025-04-25 09:26:47 +02:00
b746987712
Make eventable a generic concern and create a card's especialization for it
2025-04-24 13:07:12 +02:00
54f4bd5144
Generalize event's cards as eventable,add collection
...
Lots to tidy up but this is working
2025-04-24 12:28:16 +02:00
54375e8ded
Re-dump the schema cache file
...
using the latest Rails version, which means we should have less churn
in the file going forward.
2025-04-23 14:09:40 -04:00
bd5a41a0a1
Refresh migrations
2025-04-23 17:25:11 +02:00
2eae58725a
Remove notifications' resource relationship
...
Is confusing since "source" already captures the origin of the notifications. It's
needed to interpret things at rendering time, so we can query things as needed there.
2025-04-23 13:52:47 +02:00
696732a90a
Rename mentions' container => source
2025-04-23 13:41:34 +02:00
22df208f9a
Render proper content for mentions, don't send mentions to yourself
2025-04-22 14:11:21 +02:00
8aa99e34b4
Persist notification's creator
...
Instead of delegating. With a polymorphic relationship, relying on a certain
attribute implies doing things like aliasing "mentioner" to "creator" or similar.
2025-04-22 13:48:43 +02:00
4f06473405
Notifications for mentions showing up
2025-04-22 12:02:48 +02:00
aa3acfeaa8
Add plain text mentions
2025-04-22 11:26:56 +02:00
1114679c20
Remove activity score columns
2025-04-18 17:05:17 +02:00
abd2af3d8a
Dont need an index for a single record
2025-04-15 15:35:28 +02:00
7e5f71fedd
We will only have one account record per account
...
Not sure why this was added in the first place.
2025-04-15 15:17:30 +02:00
6bbf68a4f9
The tenanted db is the account scope
2025-04-12 20:06:34 +02:00
760cbb6c99
Drop boosts
...
Killed by design.
2025-04-12 18:52:54 +02:00
fb733b9a60
No more tracking commenting as an activity for sorting
...
We are doing away with all the automated activity scoring, but for now
lets just get rid of it for comments.
2025-04-12 10:50:25 +02:00
cbdb9aa113
Schema movement -- is this because the dumper doesnt sort deterministically? cc @flavorjones
2025-04-11 16:24:38 +02:00
7406a1039f
Add models to track gold cards and implement basic toggle behavior
2025-04-10 16:48:12 +02:00
deb987db2d
Move color column to stages
2025-04-09 15:41:36 -05:00
723e6d94f5
Rename bubbles => cards
2025-04-09 14:50:58 +02:00
16e8041524
Add unique constraint for keeping tags unique on a per-account basis
2025-04-07 11:36:34 +02:00
18419c52b8
Latest schema
2025-04-05 21:46:50 +02:00
f437aecf00
Sort completed bubbles by most recently completed first
2025-04-04 15:39:00 +02:00
0e3f756a27
Merge pull request #351 from basecamp/close-with-label
...
Close as...
2025-04-04 15:09:47 +02:00
be4a738f1d
Make reason not null
2025-04-04 15:06:43 +02:00
11d16d1c17
Move script to migration
2025-04-04 13:46:58 +02:00
77d0cd5e7f
Close as working with default fallback label
2025-04-04 10:59:53 +02:00
08cb69aca5
Replace auto_pop_at with generic last_activity column
...
so that we can use it in other scenarios
2025-04-04 09:45:56 +02:00
6b3231a535
Regenerate file
2025-04-03 19:34:05 -05:00
0820badcc3
Add involvement types to accesses
...
This provides a way to set the level of involvement that a user has with
a collection, and from which we determine the level of notifications to
send. Users can be access-only, watching, or being notified about
everything.
If you're access-only, you won't get an notifications. If you're
watching, you'll only get notifications for the items you're watching
(which includes the items you've been assigned, have commented on, etc).
If you're set to everything you'll get notifications about all activity
in that collection.
This change replaces our previous concept of subscriptions. Where
previously you'd subscribe to a collection to get notifications in it,
now you'll simply set the notification level on your access.
2025-04-03 16:35:13 +01:00
1cf2e24bcc
Set buckets at the workflow level
...
- All bubbles inherit the bucket's set workflow
2025-03-27 14:35:07 -05:00
2c87c2fb15
Update schema files and fix some trivial test failures.
2025-03-18 09:14:16 -04:00
28a569c49b
Tickets
2025-03-17 21:24:08 -05:00
d9ece38753
Make the application multi-tenant
2025-03-12 07:53:31 -04:00
Jorge Manrubia