Bulk importing issues

Bulk import issues if you demand to avert time-consuming transmission information entry or migrate data from some other system.

Y'all can also update multiple issues at once using sessions in Bulk Importer. For more data, encounter Update existing issues in bulk.

How information technology works

You download the Excel template from the Bulk Importer page in Launchpad and ready data in the template. And so, you upload the template in the Bulk Importer page.

Where are the uploaded problems?

Once yous upload issues, the data is available in:

  • the Issues tab
  • Consequence Tracker app
  • OrganizationName Project Report (the final inspect written report)
  • all of the downloadable Issues reports

Before you start

Before you can download the template, you must create a projection.

For more data, see Creating projects.

Workflow

Permissions

Only Arrangement Admins can majority upload HighBond resources from Bulk Importer.

Upload new issues in bulk

Note

Interface terms are customizable, and fields and tabs are configurable. In your example of HighBond, some terms, fields, and tabs may be different.

Download the Excel template

  1. Open up Launchpad.

    Note

    If your company uses more than one instance in Launchpad, make sure the appropriate case is active.

  2. Select Options > System.

    If you lot exercise non run into Organization as an option, the account you lot used to sign in does not take Admin privileges.

  3. Under Bulk Importer, click Manage bulk resources.
  4. ClickDownload .xlsx Template.

    The Excel template saves to your local machine (HighBond_Template.xlsx).

Gear up data in the template

  1. Open the downloaded template (HighBond_Template.xlsx) and go to the Problems worksheet.
  2. Copy and paste or enter your data into the template.

    Note

    • If you utilise Add-In for Excel, ensure the ACL Add-In selection is disabled before modifying the Excel template. To learn how to do it, see Configuring Add-In for Excel.
    • Exercise not alter the proper noun of the worksheet or the fields. These are case sensitive and must non be modified.
    • The maximum number of rows that can be uploaded at once is 900 (including all the worksheets).
    Field Description

    referenceId

    mandatory

    specifies a unique ID for the resource. This must be unique for each row in the worksheet.

    It can contain a combination of text and numbers, and the maximum length is 255 characters.

    This field is the main key for each row in the template. Y'all will need this key if you want to update this resource again.

    Note

    Reference IDs are required when you add together or update resources using the Bulk Importer. They are not bachelor when yous add together / update resources from the user interface of HighBond.

    projectId

    mandatory

    specifies ID of the project where this effect needs to be placed.

    For example:

    https://stark.projects.highbond.com/audits/90305/dashboard,

    where 90305 is the project ID.

    description

    mandatory

    specifies detailed description of the issue.

    Tip

    You can use HTML tags to format the text, such every bit <p>, <b>, etc.

    For information about issues, see Managing issues and remediation

    owner

    conditionally mandatory

    specifies name or email ID of the person responsible for the issue.

    This field is all-time suited to add not-HighBond users.

    This field becomes mandatory if ownerUser is left blank.

    ownerUser

    conditionally mandatory

    specifies user ID (UID) or e-mail ID of the person responsible for the consequence.

    To learn how to get UID of a user, see View user details.

    Yous cannot add not-HighBond users to this field.

    This field becomes mandatory if owner is left blank.

    Note that specifying an ownerUser overrides any value provided in the owner field.

    Note

    Ensure the user you want to add to this field has already been assigned to the corresponding projection / framework. To larn about assigning user roles, encounter Assigning user roles in projects and frameworks

    deficiencyType

    mandatory

    specifies the blazon of deficiency of the issue.

    The options available depend on the configuration of the project type. For more than information, see Customizing terms, fields, and notifications.

    recommendation

    specifies detailed description of the recommended actions to be taken based on the issue.

    title

    specifies title of the issue.

    severity

    specifies intensity of the issue.

    The options available depend on the configuration of the project type. For more information, run across Customizing terms, fields, and notifications.

    published

    specifies visibility of the issue:

    • Truthful: Visible to all users.
    • False: Hidden from users assigned the Contributor Tester, Contributor User, Oversight Executive, and Oversight Reviewer roles.

    The default is false.

    identifiedAt

    specifies timestamp when the issue was identified.

    The default is the current date and time.

    reference

    		 specifies ID of the issue.

    risk

    		 specifies detailed description of the risk or the impact the issue will have.

    escalation

    specifies the person, department, or organizational body that the outcome should exist brought to.

    The options bachelor depend on the configuration of the projection blazon. For more information, see Customizing terms, fields, and notifications.

    crusade

    		 specifies detailed description of what acquired the issue to result.

    effect

    		 specifies detailed description of the effect the outcome volition have on the organization.

    costImpact

    		 specifies the estimated or actual monetary toll associated with the issue.

    telescopic

    specifies the extent to which the issue affects the arrangement.

    The options available depend on the configuration of the projection type. For more information, see Customizing terms, fields, and notifications.

    executiveSummary

    		 specifies overview of the issue that typically summarizes information from other related fields, such as adventure/impact, cause, and result.

    executiveOwner

    		 specifies executive owner of the effect.

    projectOwner

    		 specifies projection owner of the issue.

    airtight

    specifies overall condition of the issue:

    • True: Closed.
    • Faux: Open.

    The default is simulated.

    remediationStatus

    specifies remediation status of the issue.

    The options available depend on the configuration of the project blazon. For more information, encounter Customizing terms, fields, and notifications.

    remediationPlan

    		 specifies detailed description of the remediation plan.

    remediationDate

    specifies deadline for the issue to be remediated past.

    Date must exist in YYYY-MM-DD format.

    actualRemediationDate

    specifies the engagement the issue was actually remediated.

    Date must be in YYYY-MM-DD format.

    retestDeadlineDate

    specifies deadline for the issue to be retested by.

    Date must be in YYYY-MM-DD format.

    actualRetestDate

    specifies the actual date when the issue was retested.

    Appointment must exist in YYYY-MM-DD format.

    retestingResultsOverview

    		 specifies detailed clarification that specifies whether or not the effect has truly been remediated.

    position

    specifies value that determines the social club in which the issue is displayed.

    Tip

    Fill in the values in sequential lodge, so that the resource announced in the same order in the application.

    entities

    specifies entities tagged to the issue.

    For more information nigh entities, meet Setting upwardly entity tagging.

    targetType

    specifies component type where this issue must be placed.

    The target type must be 1 of the following:

    • projects
    • project_files
    • objectives
    • narratives
    • risks
    • controls
    • walkthroughs
    • control_test_plans
    • control_tests
    • walkthrough_summaries
    • project_plannings
    • project_results
    • risk_control_matrices
    • testing_rounds

    The default is projects.

    Notation

    Use the exact terminology equally mentioned in a higher place.

    For information most which target ID to use for which component, see Target type and ID for project components

    targetId

    mandatory

    specifies ID of the resources where this outcome must be placed. You can find the resource ID in the URL.

    For example:

    https://stark.projects.highbond.com/audits/90305/objectives/94778, where 90305 is the projection ID and 94778 is the objective ID.

    In the targetId field, you lot can do one of the post-obit:

    • specify the project ID if you lot want to place the issue under the project (this would exist the same ID equally mentioned in the projectId field).

    • specify the component ID (objective ID in the above case) if you want to place the effect under the component of a project. Note that the project ID must exist mentioned in the projectId field.

    For information about which target ID to use for which component, see Target type and ID for project components

    customAttributes_1_term - customAttributes_northward_term

    specifies custom attribute fields 1 through n, defined in the projection type used by the project that contains this issue.

    Past default, yous will take only 1 pair of custom aspect term and custom attribute value in the template.

    You can manually add together upwards to 5 custom fields. When calculation the custom fields, ensure you follow the same naming convention as the default one, and increment by one for each add-on. For example, customAttributes_2_term, customAttributes_2_value, etc.

    For more than information, meet Customizing terms, fields, and notifications.

    customAttributes_1_value - customAttributes_n_value

    specifies custom attribute values one through n, defined in the project type used by the project that contains this issue.

    By default, you will have only one pair of custom attribute term and custom aspect value in the template.

    You lot tin can manually add up to 5 custom fields. When calculation the custom fields, ensure you follow the same naming convention as the default one, and increment past one for each addition. For example, customAttributes_2_term, customAttributes_2_value, etc.

    Notation

    • If a value begins with a square bracket or contains a comma, semicolon, or a line break, enclose the value in double quotation marks (" ").
      For example: "[2021]", "First, second asset", "This is important; this too".
    • For a multi-select field, if you want to upload multiple values, ensure you split up each value with a comma.
    • For a dropdown or a multi-select field, ensure the values are exactly the same equally the options configured in the application.

    For more than information, see Customizing terms, fields, and notifications.
  3. Save and close the template.

Target type and ID for project components

The post-obit section shows the target type and ID for the corresponding project component.

Based on the component where you desire to place the result, utilize the relevant target type and ID in the Excel template.

Closed Project

Component:Project

Target blazon: projects

Target ID: Provide project ID.

For case: https://stark.projects.highbond.com/audits/13360/dashboard, where 13360 is the project ID.

ClosedPlanning Files OR Results Files

Component: Projection > Planning > Planning Files OR Project > Results > Results Files

Target type: project_files

Target ID: Provide planning file ID or results file ID.

For instance: https://stark.projects.highbond.com/audits/13360/planning/56292, where 56292 is the planning file ID.

https://stark.projects.highbond.com/audits/13360/results/56293, where 56293 is the results file ID.

Closed Fieldwork Overview

Component:Projection > Fieldwork > Overview

Target type: objectives

Target ID: Provide objective ID.

For instance: https://stark.projects.highbond.com/audits/13360/objectives/55979, where 55979 is the objective ID.

Closed Narratives

Component:Projection > Fieldwork > Narratives > Narrative

Target type: narratives

Target ID: Provide narrative ID.

For example: https://stark.projects.highbond.com/audits/13360/objectives/55979/narratives/22422, where 22422 is the narrative ID.

ClosedRisks

Component:Project > Fieldwork > Risk Control Matrix > Risk

Target type: risks

Target ID: Provide chance ID.

For example: https://stark.projects.highbond.com/audits/13360/objectives/55979/risks/168393, where 168393 is the risk ID.

ClosedControls

Component:Project > Fieldwork > Adventure Control Matrix > Control

Target type: controls

Target ID: Provide command ID.

For example: https://stark.projects.highbond.com/audits/13360/objectives/55979/controls/1571107, where 1571107 is the control ID.

Closed Walkthroughs

Component:Project > Fieldwork > Walkthroughs > Walkthrough

Target type: walkthroughs

Target ID: Provide walkthrough ID.

For example: https://stark.projects.highbond.com/audits/13360/objectives/55979/walkthroughs/1538197, where 1538197 is the walkthrough ID.

ClosedTest plan

Component:Project > Fieldwork > Test Plan > Examination plan

Target type: control_test_plans

Target ID: Provide control exam plan ID.

For example: https://stark.projects.highbond.com/audits/39215/objectives/72348/control_test_plans/1657599, where 1657599 is the command examination plan ID.

ClosedControl tests

Component:Project > Fieldwork > Testing > Control examination

Target blazon: control_tests

Target ID: Provide control test ID.

For example: https://stark.projects.highbond.com/audits/39215/objectives/72348/round_one_testing/5102879, where 5102879 is the control test ID.

Closed Walkthrough summaries

Component:Project > Fieldwork > Walkthroughs

Target type: walkthrough_summaries

Target ID: Not bachelor in the user interface, please contact Support for assistance.

Closed Project planning

Component: Project > Planning

Target blazon: project_plannings

Target ID: Not bachelor in the user interface, delight contact Support for assist.

Closed Projection results

Component: Project > Results

Target type: project_results

Target ID: Non bachelor in the user interface, please contact Support for aid.

ClosedRisk control matrices

Component:Project > Fieldwork > Risk Control Matrix

Target type: risk_control_matrices

Target ID: Not bachelor in the user interface, please contact Support for assistance.

ClosedTesting rounds

Component:Projection > Fieldwork > Testing

Target type: testing_rounds

Target ID: Not available in the user interface, please contact Support for assist.

Upload data

Do one of the following:

  • Elevate and drop the template into the browser window.
  • ClickChoose from your figurer and select the updated template from your computer.

    Merely 1 Excel template can exist uploaded at a time (each file is validated separately).

    • Result A success or failure message appears depending on the outcome of the process, and the latest session is updated in the Sessions table

Sessions in Majority Importer

A session in the Bulk Importer is an deed of performing an import action within a given time frame past a user.

Each user session is recorded in the Sessions table. The Sessions table contains the following information.

Field Name

Description

Session ID

Session identifier. You lot tin can click on the session ID to get to a particular session.

The session ID is appended to the URL.

For example: https://stark.bulkimporter.highbond.com/import/bcc1e04e-4cd3-46d2-a8be-0b9083baccdc, where
bcc1e04e-4cd3-46d2-a8be-0b9083baccdc is the session ID.

Engagement

Shows appointment and time of the session. You tin can sort the engagement in ascending or descending order.

Uploaded By

Shows name of the user.

Status

Shows status of the upload, successful or not successful.

Y'all can click on the condition to view the import details.

File Name

Shows the uploaded template / error log.

For case:HighBond_Template.xlsx, ErrorLog.xlsx.

You can click and download the mistake log if an upload fails.

Update existing issues in bulk

Yous can update multiple items at in one case in Bulk Importer using sessions.

Note

Y'all can but update resources that y'all have uploaded using Bulk Importer.

How it works

You lot open a previous session from the Bulk Importer page. You open the template uploaded in the previous session and update the data. Then, you upload the template in the Bulk Importer page.

Important

  • Use previous sessions to make changes or correct previously uploaded data.
  • Begin a new session to upload new resources, even when they are related to previously uploaded data.

For example: You have uploaded a projection and a few objectives in a previous session. Open the same session to update those resources. Begin a new session if you lot want to upload risks, controls, or any other resource related to the projection or objectives.

Requirements before you update

Before you lot can update, you must do the following:

  1. Make up one's mind which session to select. This is required as the uploaded data is linked to a session. Therefore, y'all have to open up the session linked to the information y'all want to update. For information about sessions, run into Sessions in Majority Importer.

  2. Ensure you accept access to the Excel template uploaded in the session that you want to select. The template contains reference IDs, which are unique identifiers for each row in the template. These are required to update the data. For more information about reference IDs, encounter Prepare information in the template.

    Caution

    Data is updated based on the respective session and reference IDs. Mismatch between the session and the reference IDs may create duplicates or issue in an mistake.

Steps to update

Note

Interface terms are customizable, and fields and tabs are configurable. In your instance of HighBond, some terms, fields, and tabs may be different.

Open up a previous session

Annotation

No previous sessions will exist bachelor when you open the Majority Importer page for the first time. Y'all must upload at least in one case to encounter the session details.

For more information almost sessions, see Sessions in Bulk Importer.

  1. Open Launchpad.

    Annotation

    If your company uses more than one instance in Launchpad, make certain the appropriate instance is active.

  2. Select Options > Organization.

    If you do not see System as an option, the account you used to sign in does not have Admin privileges.

  3. Nether Majority Importer, click Manage bulk resources.

  4. Scroll downwardly to the Sessions section and click on the Session ID of your choice.

    Result The session loads with the selected session id appended to the URL.

    Note

    Ensure you select the advisable session, in which you lot want to update the previously uploaded data. Mismatch between the session and the reference IDs may create duplicates or outcome in an fault. For more than information, see Requirements earlier you update

Update information in the template

  1. Open up the Excel template uploaded in the session that you selected in the previous step. This file contains the previously uploaded data along with the reference IDs. For more data, encounter Requirements before you update

    Notation

    Ensure the ACL Add-In choice is disabled before y'all alter the Excel template, else the upload will fail. For more information nigh ACL Add-Ins, encounter Configuring Add together-In for Excel.

  2. Become to the corresponding worksheet and update the information based on the reference IDs. For more information most the fields, meet Prepare data in the template

    Note

    Ensure you update the values corresponding to the reference IDs, based on which the previously uploaded data volition be updated. Mismatch may create duplicates or outcome in an error.

  3. Salve and shut the file.

Upload information

Do i of the post-obit:

  • Drag and drop the template into the browser window.
  • ClickChoose from your reckoner and select the updated template from your computer.

    Only ane Excel template tin be uploaded at a time (each file is validated separately).

    • Result A success or failure bulletin appears depending on the outcome of the process, and the latest session is updated in the Sessions tabular array

Troubleshooting

You tin can download and check the error log from the Sessions table. Sympathize mutual bulk upload errors and learn how to prepare errors.

The following table provides a list of possible errors that may occur when uploading the template.

Error Solution(southward)
There may be more than 900 rows in the uploaded file (including all the worksheets). Remove the actress rows from the template and re-upload.
Mandatory fields may be blank or missing in the uploaded file. Ensure that all mandatory fields (marked with red and orange column names in the template) are completed.

Note

If you practise not provide information in the mandatory fields, the row is not processed.
Data format may be wrong.

Ensure that information in text fields is valid and does not exceed the maximum field length: 255 characters.

Rich text fields do not have a character limit.

Data values may be invalid or may not friction match the driblet-downward values.

For instance: The value for received and sendRecurrentNotifications fields in the Requests sheet must be True or Imitation.
Invalid fields in the template.
  • Do not add new fields to the template.
  • Exercise non remove mandatory fields from the template.
Template may not exist in expected format.

Ensure the file format is .xlsx.
Invalid worksheet names.

Practise not modify the name of the worksheet.
Session may have expired.

Refresh the page and try uploading over again.