moderated Re: Improving my workflow
Andre Polykanine <andre@...>
Hi Mark,toggle quoted messageShow quoted text
I just don't know how you organize your code, but why not to use some
issue tracking system/repository hosting like github, Gitlab or a
separate issue tracking solution like Trac? I'm pretty sure this way
you won't lose anything and you'll be able to track your progress.
With best regards from Ukraine,
Twitter (English only): @AndrePolykanine
------------ Original message ------------
From: Mark Fletcher <firstname.lastname@example.org>
Date created: , 1:55:33 AM
Subject: [beta] Improving my workflow
As I mentioned before I went on vacation, I'm thinking of ways to improve my workflow. That is, I've been thinking about how I decide what to work on and how to track all the feature requests and bug reports that come in, without constantly distracting me. Right now, there's the Trello board, but it's inconsistently updated. And there's beta's archives, which are a trove of suggestions and requests. Also, the requests and bug reports that come into support. And finally, there are the personal requests sitting in my inbox, from Enterprise users and others.
Here's what I've come up with. Please let me know what you think or if you have any suggestions.
Beta's archives become the source of truth and I deprecate the Trello board.I rely on a series of hashtags to organize and prioritize feature requests and bug reports.Every N days or so, I go through beta's archives and assign hashtags/merge threads as appropriate.If there's a request or bug report in my inbox or sent to support, I will post a new message to beta with that.
Here are the potential hashtags (all would be Use By Mods Only):
Categories: #bug, #messages, #members, #features, #calendar, #photos, #files, #chat, #database, #wiki, #profiles, #searchImplementation effort estimate: #quick, #medium, #hard, #exhardStatus: #done
I would also like a way to prioritize things, but I haven't figured that part out yet.