Jira Access Request: teleportAccessRequestId custom field is unused

[bernardjkim]

Expected behavior:

The Teleport Jira documentation indicates that the teleportAccessRequestId custom field is required and set in new Jira issues by the Teleport plugin.

Current behavior:

The custom field is neither required or even used by the Teleport Access Request plugin. The current implementation attempts to set the custom field by using the properties request field, but the proper way to set the custom field is to set the custom field id under the fields request field.

Example:
This is the current implementation that does not properly assign the custom field

{
  "fields": {
    "issuetype": {
        "name": "Task"
    },
    "project": {
        "key": "TAR"
    },
    "summary": "user requested role",
    "description": "user requested role ..."
  },
  "properties": [
    {
        "key": "teleportAccessRequestId",
        "value": "test-id"
    }
  ]
}

This would be the proper way to assign the custom field

{
  "fields": {
    "issuetype": {
        "name": "Task"
    },
    "project": {
        "key": "TAR"
    },
    "summary": "user requested role",
    "description": "user requested role ...",
    "customfield_10038": "test-id"
  }
}

Suggested Change

The custom teleportAccessRequestId field was never being used in the first place. The simplest fix would be to remove this requirement from the documentation.

Bug details:

• Teleport version: 17.0.0-alpha.4
• Recreation steps: Follow Teleport documentation to enroll a Jira Access Request plugin. Create a new access request. Observe that the created Jira issue has an empty value for the custom teleportAccessRequestId.

[ptgott]

I've addressed the docs side of this here: #49229

If this looks okay, we can remove the documentation label.