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

[John G <john -at- garisons -dot- com>]

>
> We're looking at creating a Documentation Epic and creating 'template'
> tasks that we clone and assign to the appropriate project boards. We then
> edit the clones for that project and track them on that board. But through
> the Epic, we can also track all the doc tasks on all the boards.


> We'll be developing task templates for whatever we want, but probably
> project story-specific process steps like write, copyedit, review, accept,
> publish ...


>  Starting this effort in a couple of weeks if all goes well.


>
> JG


>
>

-- 
Sent from my iPad, please excuse any automatically created mis-corrections
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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