![[Home]](http://www.bayleshanks.com/cartoonbayle.png)
Difference between revision 1 and current revision
No diff available.v_lisivka on May 8, 2019 [–]
I use just plain text file opened in plain text editor with following conventions:
---
@ prefix for tags is for CONTEXTS or PEOPLE (you can think of a person as a type of context)
---
gitlab issue ontology ideas
gitlab default labels:
bug
confirmed
critical
discussion
documentation
enhancement
suggestion
support---
gitlab Scoped labels: mutually exclusive sublabels
gitlab label priority (binary function on labels)
" If you sort by Priority, GitLab? uses this sort comparison order:
Items with milestones that have due dates, where the soonest assigned milestone is listed first.
Items with milestones with no due dates.
Items with a higher priority label.
Items without a prioritized label."State State (open or closed) Health status (on track, needs attention, or at risk) Confidentiality Tasks (completed vs. outstanding)
" Health status ultimate gold Version history
To help you track the status of your issues, you can assign a status to each issue to flag work that’s progressing as planned or needs attention to keep on schedule:
On track (green)
Needs attention (amber)
At risk (red)"related issues: can be just "related", or "blocking" or "blocked by"
Planning and tracking Milestone Due date Weight
weight in gitlab is a nonnegative integer (but i would like just any integer, with 0 being the default weight, so that you can go both above and below the default)
" Milestones in GitLab? are a way to track issues and merge requests created to achieve a broader goal in a certain period of time.
Milestones allow you to organize issues and merge requests into a cohesive group, with an optional start date and an optional due date. "
" Special milestone filters
When filtering by milestone, in addition to choosing a specific project milestone or group milestone, you can choose a special milestone filter.
None: Show issues or merge requests with no assigned milestone.
Any: Show issues or merge requests that have an assigned milestone.
Upcoming: Show issues or merge requests that have been assigned the open milestone that has the next upcoming due date (i.e. nearest due date in the future).
Started: Show issues or merge requests that have an open assigned milestone with a start date that is before today."Multiple issue boards
---
backlog, todo, in progress, in review, done, canceled priority: none, super high, high, med, low
bug/feature/improvement
---
tasks, subtasks, task relations: blocking, blockedby, related
group tasks into: task/subtask; tasks under milestone; tasks under project/department; tasks under "epic"/cross-department project
---
ready for development, in development, ready for review, ready for deploy
---
unclear backlog planned in progress completed
---
new open team_help stalled rejected resolved deleted
open resolved abandoned
---
new wip done deferred not started, outlining, wip, reviewing, done ready for review, changed requested, approved not drafted, in draft, in review, ready to publish, published planning, in beta, A/B testing not started, waiting, wip, done, on hold
suggestion: color states by Red = least done (leftmost state) to Blue = most done (rightmost state)?? Or mb green = done??
assignee, due date, priority, point of contact
new open pending(=waiting for client) on-hold(waiting) solved closed
maturity levels: planned minimal viable complete lovable see gitlab's defns: https://about.gitlab.com/direction/maturity/ " Planned: Not yet implemented in GitLab?, but on our roadmap. Minimal: Available in the product, but may not be ready for production use, yet. Viable: Significant use at GitLab? the company. CM Scorecard at least 3.14 for the job to be done (JTBD) when tested with internal users. No assessment of related jobs to be done. Complete: GitLab? the company dogfoods it exclusively. At least 100 customers use it. CM Scorecard score at least 3.63 for the identified JTBDs when tested with external users. Lovable: CM score of at least 3.95 for the JTBD (and related JTBDs, if applicable) when tested with external users. "
note: when they talk about scores, they mean average scores on a UI questionnaire from 1 thru 5
(see also NASA TRLs)
---
bug feature chore (is chore = recurring task?) process_improvement refactor
---
unscheduled, ready for development, in dev, ready for review, ready for deploy, completed backlog, to be prioritized, low impact, high impact, out of scope unstarted, started, done
not started, draft, edit, done low, normal, high, urgent open, pending, solved (like "not started, wip, done", but for support tickets) question, incident, problem, task, suggestion, other on track, at risk, off track, hold (green, yellow, red, blue) active, inactive, new, open, stalled, resolved, rejected open, overdue, completed open tasks: overdue, today, tomorrow. all tasks: open, completed new, followup, under review, demo, negotiation, won, lost analyst, competitor, customer, integrator, investor, partner, press, prospect, reseller, other how you met: networking, college, employer, hobby, service people, friends, family suggested, approved, wip, completed ---
for updates:
title, current status (on track, at risk, off track, hold), summary, what's been accomplished, what's blocked
---
due soon, overdue, aged, next action single action list, someday/maybe, projects
---
https://trello.com/b/kZsVVrc8/front-product-roadmap has: ideas, coming soon, and then an entry for each of the next 4 quarters (they have the current quarter too but it's empty, so i'm guessing that stuff was moved to 'coming soon'; so the next 4 is really what they got)
they have about 7 things in each of 'ideas' and 'coming soon', and about 10-25 items in each of the next quarters.
anyone with a trello account can vote but no one can otherwise edit it
---
from https://web.archive.org/web/20180412165759/https://blog.fogcreek.com/how-we-make-trello/ 
(backlog, i guess), bugs for this week, doing, waiting for test/review, ready for merge, staging unshippable, jellydonut-20
---
" I use todo.md, and have VIM highlight "[ ]", "[x]", "[>]", "[v]", and "[-]" for bullet-journal-like TODO, DONE, Deferred, Dropped, and FAILED, respectively. " -- https://news.ycombinator.com/item?id=21905423 Ask HN: Solo devs, how do you plan your development?
---
gmail (prioritization ontology) appears to have 2 booleans:
starred (mapped to Maildir's 'flagged' by lieer) important
---
hey.com categories according to: https://thesweetsetup.com/hey-email-disrupted-my-email-workflow/
imbox (important inbox), the feed (things like newsletters), paper trail (things like receipts), reply later (stuff you gotta answer), set aside (e.g. reference for later stuff), all files (file attachements), labels, 'screened out' (stuff that 'the screener' filtered out -- this isn't junk mail, it's just stuff that wasn't so important)
another key thing they did was have 'stickies' which are short notes shown next to emails in the index. And 'clips' which are highlights/facts from an email (like an address or account number) which appear in a list of 'clips' over all emails
---
---
https://en.wikipedia.org/wiki/MoSCoW_method
must have/should have/could have: kind of like my active/later/zzz
---
"Apple provides four QoS? levels, and a fifth which leaves it up to macOS to decide. When writing the code, the developer uses names for the levels of QoS?
