Best way to document technical writing in JIRA?

[Jessica]

What is the best way to document technical writing tasks in JIRA? It's hard to get what I'm doing to match up with the sprint process. Adding subtasks holds up the sprints because I'm not always able to get the resources I need to document a change within a sprint, even if the necessary changes are done. There are checkboxes to indicate that an issue needs documentation but they don't appear to do anything. Should I create an epic that links all the related issues that I need to document? 

[JohnA]

Hi Jan,

All of Atlassian's translations are user generated and there is certainly opportunities for you to assist with that. You can read about joining the tranlsation effort here: https://confluence.atlassian.com/display/TRANS/Atlassian+Translations

You might also find that the InProduct Translation plugin suits your needs whilst the language pack is being upgraded, you can check it out here: https://marketplace.atlassian.com/plugins/com.atlassian.translations.jira.inproduct

All the best,
John