Some problems take multiple days to solve and involves lots of research and testing. Usually I just put my findings into an email and/or a document saved with the software or code base explaining what we learned, how to reproduce the problem(s), the effects of one solution versus another, etc.., then a year later when we need to return to it I search my emails and forward it to whoever needs the information. Does any of this fit into Jira? From what I can see I'd just continuously edit the "description" part of the issue which is unwieldy to create and hard to find and read later, but has the advantage of being directly tied to the Jira issue that the findings relate to, is there something else in this Atlassian ecosystem to help me out here?
I suppose the documentation side of things might help (Confluence), but what I need isn't documentation for what a piece of software is and how a user uses it, it's documenting the steps taken to fix something and the lessons learned. When something is fixed I tell my boss high level information, "the software works now. The issue was X and I solved it through Y", but I need engineering notes to be passed on, either to my future self or someone else, that goes into detail, "Learned that the Windows SDK has a tool to track how a process exits. We need the 32 bit version for these reasons, and to launch it from the admin account for other reasons, but on our xyz system we need the 64 bit version for reasons", what's a good way to store this information for future use?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.