Jira can be used as a datasource for skills. Completing Jira issues results in acquiring or enhancing skills. This means that the title and the description of an issue can be used as data source to infer skills from. When the status of an issue is considered to be ‘Done’, i.e. set to ‘Done’ (or any equivalent), the content of the issue will be added to the profile of the employee that completed the issue. The issue can be of any type e.g. Task, Epic, Story… When the status of an issue is changed from ‘Done’ (or any equivalent) to something else, the issue will be removed from the profile of the employee that completed the issue. Issues without an assignee will not be processed for skill inference. However, issues with the status ‘Done’ (or any equivalent) that get an assignee will still be added to that assignee’s profile. The profile is also dynamically updated if the title or description of the issue changes after it was already added to their profile. An essential step in the installation process is linking Employees with their corresponding Jira users. Since an Employee’s Jira ID may differ from the external_id used in the TechWolf API, a method for mapping these IDs is necessary. This mapping can be achieved by setting a Custom Property, for each Employee within the TechWolf API, that stores the Jira ID or the email address.