Using Jira Core for Legal projects

All companies have legal obligations and requirements, often related to documentation and policy. For example, it is common for businesses to have to manage information related to employment policy, licensing, product and service terms, compliance, and all manner of other requirements.

Jira Core comes with a document approval project type for managing critical information and ensuring that content development and updates are completed. The project workflow looks like this:

About the document approval project

  • Keep track of where each document is in the update and review process
  • Attach each review version to an issue to keep track of the latest document changes
  • Easily see who is working a document and keep things moving through the review cycle

Treat each item as a document

You can treat each item that appears on your board as a document. This way you will always know the status of each piece of work.

Configure your board columns to have represent the most applicable status, such as Drafting, Review, Awaiting Approval, etc.

Set due dates

You can set a due date for each document and see how much time there is to go, or how overdue work is. Set the date when you create an issue, or add it later.

Use components to identify document groups

Jira Core comes with 'components'. Components are like sections of a project.

You can use components to identify groups of issues (or documents) so they can be managed together. For example, you could create components for 'Employee forms', 'Company policies', 'Customer Policies', etc. You can even assign specific people or groups to be responsible for certain components.

For more information, see Organizing work with components.

Common customizations

  • Add other issue types to manage the document creation process. For example, use tasks and sub-tasks to track scoping or research activities, or manage publication processes. Adding, editing, and deleting an issue type.
  • Use custom fields to record additional information about a document, such as document location, future revision date, archive schedule, etc. See Issue custom fields.
  • Change the workflow of the 'Document' issue type to suit the way your company updates documents. See Editing an issue workflow.
Last modified on Oct 27, 2017

Was this helpful?

Provide feedback about this article

Not finding the help you need?

Ask the community

Powered by Confluence and Scroll Viewport.