hardis
set-label
Description
Command Behavior
Adds a label to a ticket, without posting anything else, so that a script can flag a ticket it could not process.
- The label is added on top of the existing ones; a label already there is left as is.
- A label the ticketing system cannot store (a space on JIRA) is refused before any call.
--allowed-projects a,breads the ticket first and fails withTicketOutOfScope, writing nothing, when it belongs to another project.
Errors
TicketProviderNotConfigured, TicketProviderNotSupported, TicketNotFound, TicketOutOfScope, TicketRateLimited.
Technical explanations
- JIRA:
issues.editIssuewithupdate.labels.add, the stepticket commentandticket attachalready use. - Azure Boards: a tag. JSON patch of
System.Tags, guarded by ateston the revision read just before; tags are compared without case. - ServiceNow: a tag: a
label_entryrecord pointing at alabel, the label being created on first use (as the deployment tag). - Aha!: a tag of the feature; the current tags are read first, since Aha! replaces the whole list.
Agent Mode
The command never prompts. --id and --label are required:
sf hardis ticket set-label --id ACME-123 --label ia-qualif-erreur --allowed-projects ACME --agent --json
Parameters
| Name | Type | Description | Default | Required | Options |
|---|---|---|---|---|---|
| agent | boolean | Run in non-interactive mode for agents and automation | |||
| allowed-projects | option | Comma-separated projects the ticket must belong to (TicketOutOfScope otherwise) | |||
| debug -d |
boolean | Activate debug mode (more logs) | |||
| flags-dir | option | Import flag values from a directory. | |||
| id -i |
option | Ticket identifier (JIRA key such as ACME-123, or Azure Boards work item such as 1234 or AB-1234) | true | ||
| json | boolean | Format output as json. | |||
| label | option | Label added to the ticket | true | ||
| provider -p |
option | Force the ticketing system instead of deducing it from the identifier | jira azure servicenow aha |
||
| skipauth | boolean | Skip authentication check when a default username is required | |||
| websocket | option | Websocket host:port for VsCode SFDX Hardis UI integration |
Examples
$ sf hardis:ticket:set-label --id ACME-123 --label ia-qualif-erreur
$ sf hardis:ticket:set-label --id ACME-123 --label ia-qualified --allowed-projects ACME --agent --json
$ sf hardis:ticket:set-label --id AB-4567 --label "ia qualified" --allowed-projects "My Project" --agent --json
$ sf hardis:ticket:set-label --id INC0012345 --label ia-qualified --agent --json
$ sf hardis:ticket:set-label --id PROD-12 --provider aha --label ia-qualified --agent --json