CONTROLLED DATA
Leidos Proprietary - US Citizens ONLY
The information contained herein is proprietary to Leidos, Inc. It may not be used, reproduced, disclosed, or exported without the written approval of Leidos.

  • Created by Unknown User (johnsonli), last modified on Sep 13, 2019

Use this article when you have a customized workflow that you would like to share with other Leidos developers through the Enterprise Code Repository (ECR).

Project Jira workflows are considered non-data, they are subject to Intellectual Property (IP) and Contract review prior to sharing. Refer to ECR Sharing Code and Artifacts User Guide for a definition of ECR and the governance process.

Many times projects have created customized workflows that are reusable.  For projects that wish to share their workflows, they can be exported from Jira as XML and uploaded into ECR Bitbucket. This page describes the strategy for sharing reusable workflows.

ECR Bitbucket has a project, Miscellaneous Shareables which can contain multiple repositories that are not 'owned' by a particular project. Within Miscellaneous Shareables, there is a repository that contains generic shareable workflows.  

  • Projects can export their workflows in XML or JWB (Jira workflow), submit a request to share through the Submit Reusable Code and if approved, upload them into ECR Miscellaneous Shareables → shared-workflows repository
  • Submitting shareable workflows follows the ECR Governance workflow.  Even though Jira workflows are considered non-data, if they were developed by a specific project, there may be contract restrictions for sharing (yes, even non-data).
  • SDO ECR process must include an entry in the Enterprise Document Repository to ensure the workflows are searchable.

The figure below shows the process or approved miscellaneous shareables

MiscShareApproval


Step-by-step guide

  1. Submit a request to share your workflow through the SDO Service Desk - Submit Reusable Code.
    1. Be sure to complete the form and in the description state you are sharing a custom Jira workflow. This will expedite the IP/Contract review.
    2. Mitigate any feedback from the request.
  2. The SDO Engineering team will 
    1. Use the details from the request to start the process (create the Governance spreadsheet and submit the request to IP/Contract review)
    2. Notify requestor the opinion rendered (Approved or Disapproved) 
    3. If approved, 
      1. Export and upload your custom Jira workflow 
      2. Generate the documentation so the workflow can be discovered



The information contained herein is proprietary to Leidos, Inc. It may not be used, reproduced, disclosed, or exported without the written approval of Leidos.
CONTROLLED DATA