...
Everything is an issue of some description, and ties back to a previous “Epic”, in Jiraspeak.
Maybe we don’t have documentation of how or why or whose epic, or maybe it was something I did last week that had downstream consequences, but everything we do is attached to something bigger
“Tickets”/ tts-slate e-mail isn’t an area— in Getting-Things-Done parlance, it’s an Inbox—a place where stuff waits to be added to the workstream as a bug or a task or a story that is part of an Epic.
Documentation and client training are part of every issue. There is a bigger Training/Outreach/Knowledge Management “Area” in PARA terms, as well, but every issue also includes both.
Was thinking that we should connect Confluence → Jira but recently realized the big benefit might be pulling Jira into Confluence… Saw some videos where people created pages in Confluence to display high-level info about ongoing projects. 🤯
Jira Issue Types
...
Suggestions for structure
...