At Atlassian we also do this process, (see the Atlassian Knowledge Base), but we still haven't found a way to automate the process yet so we do it manually. However, the process is very simple because we have a template that we fill in that lists symptoms, error messages, the probable causes and steps to fix the problem so that converting a known issue into a Knowledge Base document only takes 5-10 minutes for an engineer to complete. So, the secret is definitely in the preparation of templates to ensure uniformity of the Knowledge Base and to speed up the process of converting bugs into Knowledge Base documents.
All the best,
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs