Re: best practices - JIRA fields for the docs team ?

[Robert Lauriston <robert -at- lauriston -dot- com>]

In our last couple of releases I've been mostly using labels on
engineering issues: doc### for things I need to write about,
doc###done for things I've completed.

For doc stories, if things can slip past code freeze, I create a
separate ###doc fix version.

I also use a known_issue label to indicate when I've added something
to the known issues in the release notes. I can search for that label
and quickly see if anything has been fixed.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Doc-To-Help: The Quickest Way to Author and Publish Online Help, Policy & Procedure Guides, eBooks, and more using Microsoft Word | http://bit.ly/doctohelp2015

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -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