Purchase Orders - Application setup

Setup from scratch

If you haven't used the RPO before or would like to start from the beginning then follow the steps in this article. 

1. Create a new issue type that will represent your Purchasing Orders
2. Create a new Jira core project where your Purchase Orders will live.
3. Associate your new issue type with the project created in (2) 
4. Create a Jira workflow that will represent your purchasing order process in your organisation. We recommend to download our template workflow from Atlassian Marketplace and customise it as per your need. Your workflow must meet the following requirements:
   1. There are 4 mandatory statuses:
      1. Draft
      2. Submitted for approval
      3. Approved
      4. Rejected
   2. There're 3 mandatory transitions:
      1. Draft → Submitted for approval
      2. Submitted for approval → Approved
      3. Submitted for approval → Rejected
   3. Submitted for approval → Approved  AND  Submitted for approval → Rejected transitions must be configured as hidden from user condition. See Conditions / Optional conditions/ Hide From User Condition on https://confluence.atlassian.com/adminjiracloud/advanced-workflow-configuration-776636620.html#Advancedworkflowconfiguration-conditions
5. Navigate to your Jira Universal Plugin Manager, choose Raley Purchase Orders and click on Configure button.
   1. In Jira config tab assign the following:
      1. Purchase Orders project - the project that you've created in step (2)
      2. Purchase Orders issue type - the issue type you've created in step (1)
      3. Initial (draft) status - The initial status in which issues in your projects are created. 
      4. Submitted for approval status - The status where a team member will transit the Jira ticket once they've specified all the data needed for the order (order lines and approvers)
      5. Order approved status - The status where Raley Purchase Orders app will transit a ticket from "Submitted for approval status" if it was approved
      6. Order rejected status - The status where Raley Purchase Orders app will transit a ticket from "Submitted for approval status" if it was rejected
      7. Order paid status - A status in your Jira workflow that indicates that specific purchase order was paid. Not mandatory
   2. In Company tab assign the following 
      1. Company name - name of your Company
      2. Country - your country
      3. State - your state
   3. In Employees tab - your configure your Jira users as company employees 
   4. In Departments tab - you define your company's organisational units and associate employees

Setup for already existing Purchase Order project

Raley-PO---Purchase-Order-Workflow---template.jwb