Skip to main content
Back to the connector catalogue

Connector

Jira

Outbound ticketing integration: Vigicap files tickets into it.

Your actions go into Jira as issues, in the project you name for each client, with their title and description. The issue's status is then read back: once it is done in Jira, Vigicap proposes closing the action and never closes it by itself. No ReCyF level is proposed. Pushing a ticket does not measure a client's posture.

01

What to create in the tool

The access is created in Jira, not in Vigicap.

Where to generate it

Atlassian account → Security → API tokens. Both kinds work: an unscoped token, or a scoped one carrying read:jira-user, read:me, read:jira-work and write:jira-work (no manage: scope). Because a scoped token is only accepted on api.atlassian.com, Vigicap switches to that address automatically when your site refuses the credential. Limit the account on the Jira side to the relevant projects (Browse projects + Create issues). The site URL is https://your-site.atlassian.net. The project key is the prefix of its issue keys (e.g. OPS in OPS-123).

Minimum role

Jeton d'API Atlassian d'un compte applicatif, porté ou non. PORTÉES, si le jeton en a : read:jira-user et read:me (test de connexion via /myself), read:jira-work (lecture du projet et relecture du ticket), write:jira-work (création) — aucune portée manage:, qui donnerait l'administration des projets et des workflows. Un jeton porté n'étant accepté que sur api.atlassian.com, les appels y basculent automatiquement ; l'adresse du site reste celle des liens remis au consultant. ÉCRITURE : le jeton porte les droits du compte qui l'a créé — Jira ne cloisonne pas un jeton par projet, donc le compte doit être limité côté Jira aux projets concernés (Browse projects + Create issues) plutôt que le jeton côté Vigicap. LECTURE : le même jeton relit l'issue ; aucune portée distincte n'existe, ce qui est précisément pourquoi la phrase précédente est écrite telle quelle.

Taken from the vendor's own role model, and checked before publication.

02

What to enter in Vigicap

  • Atlassian account email
  • API tokensecret

03

Per-client routing

These fields are filled in client by client: they say which account in the ticketing tool the ticket must land under. A wrong value does not fail the push — it succeeds against someone else, which is why Vigicap checks them the moment you type them.

  • Project key

    The project issues are created in — the prefix of its issue keys.

    e.g. OPS

  • Issue typeoptional

    Defaults to Task. Must exist in the project's issue-type scheme.

    Task

04

What it does, and what it does not do

ReCyF objectives it pre-fills

This connector feeds no ReCyF objective, and that is not a gap: it does not measure a client's posture.

What goes out to the tool

This connector WRITES: it creates a ticket from an action in the plan.

What comes back

The state of an already-created ticket comes back: its status, its closing date, its last activity. A closed ticket becomes a PROPOSAL a consultant confirms — never an action closed of its own accord. An agency that closes its own ticket must not be able to mark its own homework in the document an auditor reads.

How Vigicap handles your credentials.

Verification

This connector has been run end to end against a real instance of the tool, not merely tested against a mock.