Versions Compared

Old Version 2

changes.mady.by.user Anna Ciepłota

Saved on

compared with

New Version Current

changes.mady.by.user Piotr Koszela

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Default field - Labels (labels)Image Removed

...

General vs. custom configuration 

Field mapping can be configured per Jira project.

...

Not synchronized

Skills data is stored only in the App onlyapp. 

Synchronization with a "labels" field

All fields of type "label" are supported.Image Removed

...

Info

Synchronization with the "labels" field makes it possible to:

  • execute bulk changes → you can handle multiple issues at the same time and assign/remove skills

  • Search for tasks → skill information can be used in Jira searches

  • automate skill assignment → you can use 3rd party add-ons such as Script Runner and Adaptavist

Bi-directional sync

You can update the skill details in the way that you find most convenient:

  • When you add/remove a skill, a matching value is added as a label.

  • When you add/remove a label, a matching skill is added. 

Naming convention

skill#skillname → skill labels always start with "skill#," making it easy to find and add an appropriate label. Spaces between words are replaced by "_" underscore signs. Image Removed

...

Requirements

Info

You can't create a new required skill using a "labels" field. 

The app can only recognize skills that already exist in Administration > Skills.

If a user adds a skill label when no corresponding skill exists in the app, the label behaves like a standard Jira label. Retroactively adding the skill to the app won't trigger the processing of tasks that already have labels.