TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
The JIRA release notes feature literally only spits out what is in the JIRA
ticket. In my case, that means totally cryptic and incomplete descriptions
like "null pointer" or "404 error" that would be pretty much useless for
distinguishing one bug fix from another (because we get a ton of similar
error messages, but with different base causes). Sometimes the developer
who enters the bug has already fixed it and is just creating a ticket for
time tracking purposes and doesn't bother to record many details other than
a bug existed and they fixed it.
I've never worked anywhere that published their entire list of fixed issues
(since QA finds most of our bugs). So unless you either train everyone who
uses your system to write customer ready ticket descriptions or plan to go
in and clean up every single ticket by hand, it's pretty much useless.
I've seen it used in production (one of our development partners publishes
their Release Notes straight from JIRA) and I was appalled at how much of
their "dirty laundry" they were willing to hang out in public. I prefer to
manage what new features and bugs get reported in Release Notes rather than
just dump a couple hundred raw JIRAs for customers to have to wade through
to see if their bug got fixed.
On Wed, Jan 1, 2014 at 3:21 PM, Robert Lauriston <robert -at- lauriston -dot- com>wrote:
> Any hands-on reports about the JIRA release notes tool or other
> doc-oriented features?
>
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> New! Doc-to-Help 2013 features the industry's first HTML5 editor for
> authoring.
>
> Learn more: http://bit.ly/ZeOZeQ
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as jstickler -at- gmail -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
>
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and
> info.
>
> Looking for articles on Technical Communications? Head over to our online
> magazine at http://techwhirl.com
>
> Looking for the archived Techwr-l email discussions? Search our public
> email archives @ http://techwr-l.com/archives
>
