Projects and Tasks
Work within the Authoring Platform is organised into content projects and project tasks. There is a simple workflow including review steps. Authoring Services queries JIRA to provided project and task listings to the Authoring UI frontend.
There are two types of tickets within authoring projects in JIRA. These are "SCA Authoring Project" and "SCA Authoring Task". One ticket of type "SCA Authoring Project" is required per authoring project. This is how Authoring Services finds JIRA projects which should be listed within the Authoring UI.
The following configuration files can assist in setting up the ticket types and workflow for JIRA authoring projects:
JIRA Version 7 Project Configuration:
SCA-Authoring-Task-Workflow-V7.jwb
SCA Authoring Task Workflow V7.xml
JIRA Version 6 Project Configuration:
SCA-Authoring-Project-Workflow.jwbSCA Authoring Project Workflow.xml
Export of an empty sca project produced using the JIRA project configurator add-on
empty_sca_project_configurator_export.xml
Application Link
Authoring Services requires an Application Link to be created in JIRA using OAuth authentication. This allows Authoring Services to impersonate the user logged in to the Authoring UI when making JIRA changes.
The configuration of the application link is:
Field | Value |
|---|---|
| Application Name | Authoring Services |
| Application Type | Generic Application |
| Application URL | Any URL, for example the http root of your web server (Not used) |
| Display URL | Same as above (Not used) |
| - Outgoing Authentication - | - Not Required - |
- Incoming Authentication - | |
| Consumer Key | dev-authoring-services |
| Consumer Name | Authoring Services |
| Public Key | <Your OAuth Public Key> |
| Consumer Callback URL | None |
| Allow 2-Legged OAuth | true |
| Execute as | <any JIRA username> (This will not be used because the real user will be impersonated) |
| Allow user impersonation through 2-Legged OAuth | true |