Page Comparison

You can manage your Jira shares via web API by generating API Key. To do this, perform the following steps:

1. Go to the External Share for Jira admin panel and click on the API Keys tab. This will send you to a screen with all previously generated keys.

   

   Click on Create new API key. API key creation popup will appear.

   

2. Setup your API key and copy or download it. The template has the following fields:

   • Key Name - provide your own name for the API key, up to 40 characters long.

   • Key Value - non-modifable field, shows the value of the key.

   • Reveal - reveals the key. This is NOT one time operation - you can reveal the key at any time.

   • Download - downloads the key to the selected location.

   • Get Shares - determines whether get operation is allowed for the key.

   • List Shares - determines whether list operation is allowed for the key.

   • Create Shares - determines whether create operation is allowed for the key.

   • Not valid before - set the start date for key validity.

   • Not valid after - set the invalidation date for the key.

   • Allowed IPs - set IPs or IP range that can use the key.

   • Description - description of the key. Maximum 4000 characters.

   • Creation Time - non-modifable field, the time when the key was created.

   • Last Modification Time - non-modifable field, the time when the key was last modified.

   • Last Usage Time - non-modifable field, the time when the key was last used.

   • Usage Count - non-modifable field, counter that shows how many times the key was used.

...

With key generated, you can now make a call to Web API. First of all, set Authorization and Content-Type headers in your REST client.

...

This operation allows you to retrieve a sorted list of shares based on the options passed. You need to have an access to shared issues to be able to list shares. You can pass the following options as request parameters:

• sort - share field by which the list will be sorted. The default value is “id”. In general, you can sort by any Share’s field as long as it is in a snake_case instead of camelCase. For example, you can sort by Issue ID, by passing “issue_id” (instead of issueId as returned in the JSON).

• sortOrder - order in which list will be sorted. Pass “asc” for ascending list; “desc” for descending list. “asc” is default.

• limit - defines how many shares will be returned in a single call. Default is 100.

• offset - defines how many positions from the start of the list will be ommited. Combined with the limit parameter, this parameter may be helpful in performing help perform concurrent calls. The default value is 0, which means the very first share on the list will be returned.

• userId - returns all shares for a given user ID.

• projectId - returns all shares in the selected project.

...

...

POST https://jira.external-share.com/webapi/share
{
	"issueId": "10001",
	"type": "ISSUE",
	"expiration": 1649700933954,
	"customFields": [{"id":"10020"}, {"id":"10021"}],
	"allowExternalUsers": true,
	"externalUsers": ["expl@expl2.com", "expl@expl.com"]
}

An example rule: Automatically create an External Share link for every new issue.