highbond_request_item (Resource)

Example Usage

resource "highbond_request_item" "main" {
  description                  = "<h1>Description heading</h1><p>Request item description.</p>"
  owner                        = "Sowmya Balamkar"
  owner_email                  = "sowmya.balamkar@wegalvanize.com"
  due_date                     = "2020-06-01"
  send_recurrent_notifications = false
  email_subject                = "Email subject"
  email_message                = "Email message"
  position                     = 1
  received                     = false // Deprecated, please use the request_item_status instead of this
  request_item_status          = "Open"
  cc_contacts                  = ["biswaranjan.behera@wegalvanize.com", "robots-qa@wegalvanize.com"]
  force_updates                = true // Create only with force update changes
  target {
    id   = highbond_objective.main.id
    type = "objectives"
  }
  requestor_user = "Enter a valid UUID here"
  owner_user     = "Enter a valid UUID here"
  cc_users {
    id = "Enter a valid UUID here"
  }
  cc_users {
    id = "Enter a valid UUID here"
  }
  // Can not use contact_reference values when owner_user is there
  contact_reference_name      = "Biswaranjan"
  contact_reference_email     = "biswaranjan.behera@wegalvanize.com"
  contact_reference_table_id  = "357115"
  contact_reference_record_id = "1548451013698540"
  project_id                  = highbond_project.main.id

}

Schema

Required

• description (String) Describes the requested information, such as the document name, version number, or department where you might expect to find the information
• project_id (Number) The ID of the project
• requestor_user (String) The unique identifier (UID) of the user requesting the documentation

Optional

• cc_contacts (List of String) Specifies one or more people that can contribute to the request. A comma separated list of email addresses
• cc_users (Block List) (see below for nested schema)
• contact_reference_email (String) Specifies the email of the contact reference for fulfilling the request. Should be provided together with other contact reference fields. Values in contact reference fields will override any values provided in the owner and owner_email, but will not override owner relationship
• contact_reference_name (String) Specifies the name of the contact reference for fulfilling the request. Should be provided together with other contact reference fields. Values in contact reference fields will override any values provided in the owner and owner_email, but will not override owner relationship
• contact_reference_record_id (String) Specifies the record_id of the contact reference for fulfilling the request. Should be provided together with other contact reference fields. Values in contact reference fields will override any values provided in the owner and owner_email, but will not override owner relationship
• contact_reference_table_id (String) Specifies the table_id of the contact reference for fulfilling the request. Should be provided together with other contact reference fields. Values in contact reference fields will override any values provided in the owner and owner_email, but will not override owner relationship
• due_date (String) Specifies when the request should be fulfilled by
• email_message (String) Provides the ability to customize the body of the email
• email_subject (String) Provides the ability to customize the email subject line.
• force_updates (Boolean) Allows overriding top-level 'create_only' option.
• owner (String) Specifies the name of the person responsible for fulfilling the request. If the person is not a user or contact in a HighBond instance, you can provide a value in this field on create or update. This field becomes required if the owner_user relationship is not provided
• owner_email (String) Specifies the email of the person responsible for fulfilling the request. If the person is not a user or contact in a HighBond instance, you can provide a value in this field on create or update
• owner_user (String) The unique identifier (UID) of the user responsible for fulfilling the request.
• position (Number) The value that determines the order in which it is displayed. position must be a value between 1 and 2147483647
• received (Boolean, Deprecated)
• request_item_status (String) Specifies the status of the request item.
• send_recurrent_notifications (Boolean) Sends an email to the request owner and CC'ed persons on a specified recurring schedule. For more information about recurring reminders
• target (Block List) Specifies the resource that the request item is associated with (see below for nested schema)

Read-Only

• created_at (String) The timestamp identifying when the request item was created
• id (String) The ID of this resource.
• requestor (String) Specifies the name of the person requesting the documentation
• updated_at (String) The timestamp identifying when the request item was last updated

Nested Schema for cc_users

Required:

• id (String) Specifies one or more users in a HighBond instance that can contribute to the request

Nested Schema for target

Optional:

• id (String) The ID of the resource
• type (String) A target can have one of the following types: projects, controls, control_tests, control_test_plans, issues, narratives, objectives, walkthrough_summaries, project_files, project_plannings, project_results, risks, risk_control_matrices,testing_rounds, walkthroughs