<p><span class="error">The license could not be verified: License Certificate has expired!</span></p>

Skip to end of metadata
Go to start of metadata

The license could not be verified: License Certificate has expired!

1. Table of Content

 

 

2. Basic information

2.1. Purpose of the add-on

Forms for JIRA add-on (hereinafter referred to as JFs) enable quick and easy JIRA issue creation from within the Confluence page (page embedded form).

2.2. Macros

Macro

Description

jiraforms

define form's fields with JFs attribute pool

2.3. Prerequisites

There are some elementary preconditions to be met:

  1. Application links are to be set properly on both sides (JIRA and Confluence).
  2. Create Issue permission has to be set correctly in JIRA project's permission scheme (according to use of project attribute, see below).
  3. Assign Issues and Modify reporter permissions are to be set correctly in JIRA (according to use of assignee and reporter attributes, see below).
  4. Usernames in JIRA and Confluence are to be matching if using reporter attribute.

2.4. Licensing

2.4.1. Free Trial

Take the benefits of a free trial period first. The add-on is fully functional, however it is time-limited to 1 month from installation. At the cessation of that period, functionality of JFs will be partially locked (see below) and a message will be displayed linking to the Atlassian marketplace where a full license can be purchased.

2.4.2. Full license

The license is valid for one year. After that, some JFs functionality will be inaccessible (see below), hence license renewal is necessary.

2.4.3. Differences between licensed and unlicensed version

FunctionsUnlicensedLicensed
Creating issues from Confluence(tick)(tick)
Working with standard JIRA fields(tick)

(tick)

Issue Linking(error)(tick)
Attachment(error)(tick)
Working with JIRA Custom fields(error)(tick)

 

3. Working with JFs

There are two roles defined to work with JFs. These roles are derived from user groups in Confluence.

3.1. Confluence Administrator

The user is a member of the group confluence-administrators and has the correct permissions

  • to install the plugin (Confluence Administration > Manage Add-ons ), 
  • to insert a valid license key,
  • to set up trusted connection between JIRA and Confluence and
  • to select the proper Application links that will be used.

3.1.1. Installation

Easily install the add-on via Confluence UPM or by manual download from the Atlassian Marketplace. Installation and basic configuration fall within Confluence administrator's authority only.

3.1.2. License key

Trial license can be obtained via Atlassian Markeplace or within standard UPM functionality (Confluence admin > Manage Add-ons > Forms for JIRA > Free Trial ).

Full license can be ordered from the Atlassian Marketplace ( or directly from within the Confluence via standard UPM functionality: Confluence Admin > Manage Add-ons > Forms for JIRA > Buy Now) .

3.1.3. Add-on configuration

1. Check / define Application Links

A working connection between JIRA and Confluence instances has to be made on both sides via Administration > Application links.

Check the Application links and set up Outgoing authentication / Trusted applications (see Troubleshooting).

 

2. Use the existing application link

Choose from existing connections in Confluence Administration > Manage Add-ons > Forms for JIRA > Configure.

3.2. End user

The end user defines JIRA issues-creating form and embed it directly within the desired Confluence page using Jiraforms macro and the pool of proper attributes (see below). Form's functionality depends on the target JIRA project's permission settings.

You must specify at least one parameter "config" or "id".

3.2.1. Form definition (the proper use of attributes pool)

Set of attributes, which can be used for the issue-creating form macro configuration (the config parameter).

Each field's definition is ended by a semicolon (see samples below). Particular field attributes are comma separated.

Attribute

Description

Example

TITLE

Field label (displayed to the left of the field)

title=Task Purpose

KEY

JIRA issue field mapping

  • project (warning) required (single-select only)
  • summary
  • issuetype
  • assignee
  • reporter
  • priority
  • labels
  • originalEstimate  
  • versions
  • environment
  • description
  • duedate
  • fixVersions
  • components
  • attachment
  • watchers
  • custom:$customfieldID (info) identify the customfield by ID (after the colon), (warning) only text and datepicker types supported

Keys needed for issue linking:

  • linkType - (info) link type used between issues.
  • links - (info) list of issues to link to.

 

key=project

 

key=reporter

 

 

 

 




key=custom:10182

TYPE

Defines the field’s data (value) type. Green items represents dynamic JIRA sources for obtaining the list-of-values (mostly based on single project selection via key attribute, see above). 

  • TEXTFIELD
  • TEXTAREA
  • CHECKBOX
  • DATEPICKER
  • FILE
  • ENUM (info) set the list of values manually
  • GROUP
  • USER
  • ISSUETYPE
  • COMPONENTS
  • VERSIONS
  • ASSIGNABLE
  • PRIORITY
  • LINK_TYPE

Source of issues to link with (KEY=LINKS)

  • type=ENUM:$issueKey1:$issueKey2:$issueKey3 (info) Insert the list of values manually ...
  • type=FILTER_RESULT:$filterID (info) ... or insert the ID of the existing JIRA filter.

type=checkbox
type=datepicker
type=assignable








key=linkType, type=link_type

key=links,
type=ENUM:TST-1:TST-2

key=links, type=filter_result:10301

DEFAULT

Implicit field value (static or dynamic)

  • ID
  • string

 

 


Issue Linking

  • $issuelinkID-inward 
  • $issuelinkID-outward

Set current (logged in) Confluence user as a (JIRA issue) reporter dynamically

  • $currentUser


key=components, type=components,default=1475

key=description, default=some description goes here...

 


default=10320-inward
default=10320-outward

 

key=reporter, default=$currentUser

VISIBILITY

visibility of the field

  • visible (info) (default)
  • disabled
  • hidden

 

visibility=hidden
visibility=disabled
visibility=visible

MULTIPLE

Possibility to set multiple choice (multi-select from lists of values), if applicable. (info) Allowable values:

  • true (1) 
  • false (0)

 

multiple=true
multiple=0

MANDATORY

Possibility to set mandatory form fields.

  • true
  • false

 

mandatory=true

3.2.2. Enabled combinations of keys and types

For every key is a set of types enabeled. It is not possible to combine every key with every type. Table of enabled options is bellow.

Note: meaning of symbols used in the table:

x - preferred combination

o - possible combination 

Key \ Type

T

E

X

T

F

I

E

L

D

T

E

X

T

A

R

E

A

D

A

T

E

P

I

C

K

E

R

F

I

L

E

I

S

S

U

E

T

Y

P

E

C

O

M

P

O

N

E

N

T

S

V

E

R

S

I

O

N

S

P

R

I

O

R

I

T

Y

S

E

C

U

R

I

T

Y

A

S

S

I

G

N

A

B

L

E

U

S

E

R

F

I

L

T

E

R

_

R

E

S

U

L

T

L

I

N

K

_

T

Y

P

E


E

N

U

M


N

U

M

B

E

R

project

cannot be edited, must be hidden

summaryxx           o 
issuetype    x        o 
assignee         x   o 
reporterx        ox  x 
priority       x     o 
labelsxx           x 
originalEstimatex            x 
security        x    o 
versions      x      o 
environmentxx           x 
descriptionxx           o 
duedate  x          o 
fixVersions      x      o 
components     x       o 
attachment   x           
linksx          x x 
parentKeyx          x x 
linkType            xo 
watchersx        xx  o 
customxxx xxxxxxxx xx

Table: Enabled combination of atributes and types

3.2.3. Sample form definitions

The following are some examples of JIRA issue creation form definitions.

3.2.3.1. Example A - basic issue fields (incl. multiple selection and customfield)

 

Source code

 

3.2.3.2. Example B - Issue linking

There is a possibility to link newly created issues to existing issues during creation. The example below shows how this can be achieved.

Source code

4. Troubleshooting

4.1. Application link was not found (No application link with name ...)

Issue

Instead of embedded form, Confluence displays the error message "No application link with name .................".

Solution

Choose the right application link (see chapter 3.1.3) or configure the new one to be (Confluence Admin -> Administration -> Application Links):

  1. Edit proper application link:

  2. Outgoing Autentization -> Trusted Applications. Probably there is no configured connection, there:

  3. Scroll down and click to Enable.

  4. The connection was configured, check again:

  5. Form should be displayed:

Labels
Write a comment…