Add-ons

Two-factor authentication

Secure Login (2FA) – Jira

Ensure limited access for authorized persons only via enhanced security: in addition to the username and password, a registered mobile device will be used each login time to generate a PIN code valid for half a minute.

The default login for Atlassian tools on-premise is based on username and password only: this is not a secure authentication as both values can be easily passed and copied to other persons using them in parallel to the owner. A secure login depends on multiple aspects and combines knowledge with physical gadgets, so it is not possible to duplicate it. On the other hand, if someone steals such a gadget, it is useless without the knowledge aspect. Using the "Secure Login" app for Atlassian server products, a mobile device as keycode generator respectively authenticator or a Yubikey (USB-based device) can be used as 2-factor to ensure proper identification of logged in user.

Secure Login (2FA) – Confluence

Ensure limited access for authorized persons only via enhanced security: in addition to the username and password, a registered mobile device will be used each login time to generate a PIN code valid for half a minute.

The default login for Atlassian tools on-premise is based on username and password only: this is not a secure authentication as both values can be easily passed and copied to other persons using them in parallel to the owner. A secure login depends on multiple aspects and combines knowledge with physical gadgets, so it is not possible to duplicate it. On the other hand, if someone steals such a gadget, it is useless without the knowledge aspect. Using the "Secure Login" app for Atlassian server products, a mobile device as keycode generator respectively authenticator or a Yubikey (USB-based device) can be used as 2-factor to ensure proper identification of logged in user.

Secure Login (2FA) – Bitbucket

Ensure limited access for authorized persons only via enhanced security: in addition to the username and password, a registered mobile device will be used each login time to generate a PIN code valid for half a minute.

The default login for Atlassian tools on-premise is based on username and password only: this is not a secure authentication as both values can be easily passed and copied to other persons using them in parallel to the owner. A secure login depends on multiple aspects and combines knowledge with physical gadgets, so it is not possible to duplicate it. On the other hand, if someone steals such a gadget, it is useless without the knowledge aspect. Using the "Secure Login" app for Atlassian server products, a mobile device as keycode generator respectively authenticator or a Yubikey (USB-based device) can be used as 2-factor to ensure proper identification of logged in user.

Secure Login (2FA) – Bamboo

Ensure limited access for authorized persons only via enhanced security: in addition to the username and password, a registered mobile device will be used each login time to generate a PIN code valid for half a minute.

The default login for Atlassian tools on-premise is based on username and password only: this is not a secure authentication as both values can be easily passed and copied to other persons using them in parallel to the owner. A secure login depends on multiple aspects and combines knowledge with physical gadgets, so it is not possible to duplicate it. On the other hand, if someone steals such a gadget, it is useless without the knowledge aspect. Using the "Secure Login" app for Atlassian server products, a mobile device as keycode generator respectively authenticator or a Yubikey (USB-based device) can be used as 2-factor to ensure proper identification of logged in user.

Automation and Workflows

Status-Sync for distributed workflows

Status-Sync for distributed workflows

Reduce manual efforts and enhance transparency by keeping the status of issues on different hierarchy levels automatically in sync for epic/stories, parent/subtasks or linked issues.

Using Jira Core, Jira Software or Jira Portfolio, you end up having hierarchies of issues. Generally, these issues are of different issue types having their own workflows and statuses. Nevertheless, there are points in time, sometimes named "quality gates," when the state of different issue levels should synchronize: you can do this manually, but it is failure-prone and not effective. Once configured, "Status Sync" automatically takes care of setting the proper status of all dependent or linked issues.

GDPR Tools

GDPR Tools_Unused Avatar Remover

Unused Avatar Remover

The "Unused Avatar Remover" allows administrators to configure a recurring Jira service to automatically delete all avatar images from the disk of deactivated or removed users without manual efforts.

Ensure the right to one's own picture as part of privacy and rights in the personality: valid since May 25th, 2018, the new General Data Protection Regulation (GDPR) instructs companies to protect data and privacy of individuals in addition to common copyrights on images. Deactivating or deleting users will not remove their avatars respectively uploaded images: they remain on disk forever. As an administrator, automate the removal of personal pictures in the form of avatars of deactivated or deleted users.

Personal Activity Stream Hide

Personal Activity Stream Hide

Protect your user's privacy by disabling the personal activity stream to prevent misuse of personal working schedule or performance: other JIRA functions refer to the stream data will still be working.

On user profiles, you can focus on reading about individual activities. That's a typical scenario for misuse: the "Personal Activity Stream Hide" helps you to protect your user's data by disabling the personal activity stream on user profiles. In many countries, worker councils also prohibit measuring the performance of individuals from work records and monitoring of activities by time stamps. Deactivating personal activity streams prevents unnecessary conflicts in this context. Also, General Data Protection Regulation (GDPR) instructs companies to protect data and privacy of individuals.

Issue History Item Remover

Issue History Item Remover

Be able to remove individual history items of an issue as administrator to prevent "hate speech" or other information being logged within the history, which must be deleted due to, e.g., regulatory requirements (GDPR).

General Data Protection Regulation (GDPR) instructs companies to protect data and privacy of individuals. Jira's issue history stores such data: what has been modified or removed when by whom. Everybody being able to view an issue can also see that issue's history, which also includes data being removed from issue fields like personally identifiable information (PII). Independent from GDPR you can protect your users and customers from "hate speech" by additionally deleting undesired comments and field contents from the issues' history. The "Issue History Item Remover" allows administrators to delete individual history items cleaning up data properly.

Interested?

Call me or write me

Frank Polscheit

Managing Director

Phone: +49 6122 9176 0