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 Jan 21, 2020

On demand or during release documentation processing, the storefront project will export and deliver a dump of all Jira issues.

Step-by-step guide

  1. Upon receipt of notification that we need to deliver a full export of Jira data to DISA, open a ticket with the SDO helpdesk to request the creation of the export file. The SDO helpdesk will use the Jira Project Configurator plugin to generate the export.

    Export File Contents

    Export includes

    Configuration: custom fields, screens, schemes, and workflows
    Issues: all issues (epics, features, stories, etc.)

    Export does NOT include

    Jira users and groups - although the user names are still included in the issues as strings/identifiers

  2. Request the SDO helpdesk upload the export file to the GSMODSF confluence page here: Jira Exports

    Exports File Access Control

    The Jira Exports page on Confluence has restricted access to control who receives or can use the data. The following people have read/write access to the page. All others have no access.

    Johnson, Lisa G. [US-US] - Mandatory R/W so Lisa can upload export files for us

    List the email accounts of the users you want to have read/write access.
  3. Once notified of the confluence upload, pull / download the file to your local workstation in preparation for delivery to DISA. Make sure the export file name follows a convention that includes the date of the export (e.g. GSMODSF-full-project-export-YYYYMMDD.zip)

  4. Create a README file that describes the contents of the export file. The README file should be similar to identical to the following. This README file should be named with the following naming convention (JiraExportYYYYMMDD.README)

    //PROJECT_NAME Export Details

    Jira: Version: 7.10.1#710002
    Project Configurator for Jira Add-on: version 3.0.10
    Project Configurator Vendor: Adaptivist.com LTD

    Filename: GSMODSF-full-project-export-20190912.zip
    Uploaded to: sdosandbox.leidos.com/display/GSMOD/Jira+Exports

    Did not export users or groups -- this should make it easier to import and avoid user mapping issues.
    Assignee names are still part of the issue and are not lost.

    Export includes
    Configuration: custom fields, screens, schemes, and workflows
    Issues: all issues (epics, features, stories, etc.)

    Export date: 12 Sept 2019 10:35 AM Pacific
    Export POC: Your Name your.email@leidos.com

    Deliver To:
    Herrick, Harold L CIV DISA SD (USA) <harold.l.herrick.civ@mail.mil>,
    Ceverino, Nicole L (Nikkey) CIV DISA BDC (US) <nicole.l.ceverino.civ@mail.mil>,
    Himebaugh, Marc S CIV DISA SD (USA) <marc.s.himebaugh.civ@mail.mil>

  5. Login to the DoD Secure File Access (SAFE) web application using your DoD CAC Card: https://safe.apps.mil 

    Access to SAFE from LeidosNet

    Note: The SAFE web site is inaccessible from LeidosNet VPN. Please disconnect from VPN prior to attempting to access the SAFE application.

  6. Follow instructions on the SAFE web site to drop off files to the recipients named in the README file as shown above. Add all recipients to the SAFE drop off form.
  7. After the SAFE drop off is completed, remove the files from the Jira Exports confluence page to reduce storage requirements of Confluence.

 





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