What are the best practices for defining workflow for documentation and localization tasks?

Almost every issue needs a documentation subtask.

Many issues need a localization subtask.

Should documentation and localization issues have their own workflow?

Should each project have documentation and localization components, so that those issues would be automatically assigned to the component owner?

Should "Create Issue" screen have a checkbox "Needs documentation", which would create a documentation subtask with specific fields?

1 answer

I would recommend using a mandatory select list say Documentation required: Yes, No, Not Applicable. Similarly for Localisation. This way everyone has to select this field and if it is not required the reporter must select Not Applicable.

This is the simplest implementation, with the help of two custom fields.


Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

24,223 views 2 7
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you