Here is my situation. Our Release Mgmt group is responsible for final testing and all training as well as end user documentation. We create a ton of issues and a sub set of those issues when completed will need some form of end user documentation developed. Since the Release Mgmt team is somewhat disconnected from the development team there is a struggle to effectively communicate what we have built that requires some documentation. My thought was that on any issue that needs to have some end user documentation assembled we could just create a sub-task called documentation and then assign that task to that specific team lead. Then all of those documentation tasks could be seen in a specific filter and on a their own board so they can work those tasks through their own series of sprints. There are a couple of problems with this that I can see and don't yet know how to solve. If the documentation task is started and then completed in a separate sprint by a separate team will that negatively impact my dev team velocity? Can I automatically assign the documentation task to a specific team lead? Instead of using a task or sub-task should I create a related issue and have a custom issue type called Documentation? Any feedback, guidance or best practices will be greatly appreciated.
