e0aa1d257e
Drop User.system and replace with Account#system_user
2025-11-24 13:23:57 -05:00
86932803e4
Clarify not now move actions copy
2025-11-24 12:03:34 +01:00
03a345609e
Baseline replacing collection with board across code
2025-11-05 13:31:54 +01:00
6d2a919a88
Typo
2025-10-29 11:00:19 -05:00
e594f89919
Add missing events to comment thread
2025-10-29 10:51:47 -05:00
95e48e9053
Prefer double quotes
2025-10-29 10:17:47 -05:00
8ca9e80c6c
Settle on "Moved to Done"
2025-10-17 16:56:26 -05:00
da413e7540
Remove closure reasons
2025-10-15 16:15:56 -05:00
1d1a3da9cf
Cleanup workflow/stages
...
This was pending after moving to columns
2025-10-07 11:10:10 +02:00
a213ac666e
Revert sentence structure, but keep bold text
2025-07-28 12:24:49 -05:00
8e795f183d
Update system message to highlight verbs
2025-07-24 13:42:19 -05:00
84fdeb4a5e
Track events when reopening cards
2025-06-04 17:18:01 +02:00
c1cc1f8fca
Track events for changing collections
2025-05-29 22:54:28 -05:00
c6c9e0d5fc
Rework system events
...
- Restyle system events so they don't look like comments and aren't attributed to the system user
- Ensure the event creator is included in the description so it's clear who did it.
- Walk back system comment replacement. Yes, it potentially avoids embarassing people when they change their mind, it's also losing data. If two intentional assigments happen in proximity, we've been only showing the latest one,.
2025-05-28 15:26:41 -05:00
29fb57ac36
Event comments should reference the actual assignees
2025-05-16 13:57:26 +02:00
d9acafcb64
New line
2025-04-30 11:05:58 +02:00
174bb21b8a
Drop event summaries too
...
We'll regenerate with a script
2025-04-30 09:55:29 +02:00
e1347bec3f
Extract method
2025-04-30 09:47:05 +02:00
b6c3e5c090
Add tests and clean unused events
2025-04-30 09:45:41 +02:00
6f06fb2277
Format
2025-04-30 08:25:06 +02:00
9edffe2170
Format
2025-04-29 20:39:55 +02:00
4ff55df2e0
Create system comments on events
2025-04-29 20:33:07 +02:00
Mike Dalessio