The main workaround for the lack of a sig or logging functions in CheckVist is to make use of the colors feature.
The main workaround for the lack of a sig or logging functions in CheckVist is to make use of the colors feature.
I assigned black, red, blue, and green to my first four workers so that they can self-identify (though only on a line-by-line basis, because color, unlike bold or italic, applies to the entire line...which makes it impossible, for instance, to signal one's edits of other team member's work).
When more workers came into my project, I started assigning the outline colors, which was even more kludgey, because that styling dominates so much, visually.
With more than 7 people, there is no way to self-identify.
CheckVist could at least aid this workaround by enabling more colors (violet? orange? brown?) with the 7, 8, 9, and 0 keys. Preferably font colors, rather than outline.
More effective, of course, would be to add tools to make collaboration truly feasible. But, meanwhile, this help with the workaround would be easy and appreciated.
I assigned black, red, blue, and green to my first four workers so that they can self-identify (though only on a line-by-line basis, because color, unlike bold or italic, applies to the entire line...which makes it impossible, for instance, to signal one's edits of other team member's work).
When more workers came into my project, I started assigning the outline colors, which was even more kludgey, because that styling dominates so much, visually.
With more than 7 people, there is no way to self-identify.
CheckVist could at least aid this workaround by enabling more colors (violet? orange? brown?) with the 7, 8, 9, and 0 keys. Preferably font colors, rather than outline.
More effective, of course, would be to add tools to make collaboration truly feasible. But, meanwhile, this help with the workaround would be easy and appreciated.
Hello Jim, to identify the last person who edited a list item, you can use 'sd' keyboard shortcut. This enables a mode when last editor is shown.
ReplyDeleteIf you want to mark list items manually (like with colors), you can also use @assignee or #tags syntax at the end of the list item. Given that you're a PRO customer, you can even assign colors to tags (but tag colors are individual).
Also, for the recent changes in the list, you can get instant e-mail notifications, where you can see who did what in the specific list.
Hope this helps,
I'm aware of "sd". If you were to use your software with a collaborative team, you'd find this insufficient for distinguishing between contribs and communications from different team members. For example, I could write 750 words, and someone else might correct a spelling, and that second person would be "credited". Also, colors distinguish at a glance. In ambitious projects it's important to quickly ascertain who's saying what.
ReplyDeleteTags are worse. A profusion of tags is a sloppy, kludgey way to determine who is writing, who is editing, who is contributing. They just create a mess.
Instant notifications are helpful, but if I'm looking at a project page and need to know who's talking (which I do roughly eight hours per day as we create my project), it is an extreme kludge to have to dredge through my email to try to find out. Can't imagine you really think that's the tool for the job.
These suggestions are inadequate workarounds for a serious deficiency. Color is a much superior workaround. Until you fix the underlying problem of clearly identifying contributors, adding some more colors would be the lowest-fruit improvement you could make.
I was preparing a reply to this, answering your questions and trying to explain the shortcomings. But I have no personal stake in you or your product (my project will complete before changes could be made even if you wanted to make them), and I seem to be upsetting you (which wasn't my intention), so it would probably be pointless to take the time.
ReplyDelete