create_credential
Attach a secret — a password, a key, a test login — to an issue or a wiki page, instead of writing it in a comment or a description, where everyone on the project reads it for ever. Pass issueKey or pageId, and a 'name' saying what it is. It can be read by the person whose token this is, by the people in 'readers', and by the project's lead, who reads every secret in the project — and by nobody else, however much of the issue they can see. The answer lists them in 'readableBy': say that to the person rather than 'only you'. There are two ways to give the value. WITHOUT 'value' nothing is stored and the answer is a 'form' link: it opens the attach dialog with the name and the readers filled in, and the person types the value there themselves. Prefer that whenever the value is not already in the conversation — a value that passes through you stays in your context and in your client's logs. WITH 'value' the secret is stored now and the answer carries its id and name, never the value; it is recorded against the token you are using. Do not repeat the value in any text you write — a comment, a description, a merge request, a log. A name in 'readers' that is unknown or cannot open the project is not stored and comes back in 'dropped' with the reason. Needs the right to edit the issue or the page.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | What it is, e.g. 'stand admin password'. Read by everybody who may read the secret, so not the value and no part of it. | |
| value | No | The secret itself. Leave it out to get a 'form' link where the person types it themselves. | |
| pageId | No | Wiki page id. | |
| readers | No | Who else may read it, comma-separated usernames or emails (see list_users): 'ivan,olga'. Leave it out for nobody else. | |
| issueKey | No | Issue key, e.g. 'UK-1'. |