Archive

Released on November 23, 2023

New Features

Portal Creator

The new CREATOR Portal role is now available. Portal Creators have more power than standard Portal Users, but less than Portal Admins. In short, the 3 available roles are best explained like this:

• USER can only access projects for which a role was assigned to him or her.

• CREATOR can create all kinds of entities like users, projects, organizations and technical users.

• ADMIN has full-access. Can create, edit and delete all kinds of entities.

Like a normal user, if the CREATOR is a member of the default organization, he can see all users and organizations. Members of other organizations can only see users of their own organization and additionally users which share a project membership with them. There's no exception on this for CREATORs.

In detail, the CREATOR (German: Ersteller) is allowed to:

• Create Projects
• Create Users (but no Portal Admins or Creators)
• Create Tech Users
• Create Organizations
• Reinvite Users (but not forcing an activation)
• See Tech Users with no role assigned (Project count 0)
• See all Organizations to be able to create new users in any organization
• View additional information on user detail pages like Portal ADMINs can
• See remaining licence counts on the pages Projects, Users and Tech Users (but doesn't have access to the Administration menu)

Since the CREATOR can only see projects where he has a role, he is automatically assigned to be a Project Admin for any new project he creates. After adding another Project Admin to a project, he can decide to remove himself.

The CREATOR cannot edit any entity after creation. If by mistake something wrong has been entered in the creation dialog, he has to ask a Portal ADMIN to fix it.

The CREATOR role is the ideal role for somebody who has to onboard some new users and create projects for them. It can make sense to grant the CREATOR role for a limited time to a project manager to improve the self-service. When he has finished setting up new users and projects he could be set back to be a standard user by any Portal Admin.

Known Issues

• Unfortunately, the links to Agile Board and Backlog in the Jira tile of the DevOps Portal homepage do not work properly for users which have more than one project. In fact, the links will lead to the last visited agile board on Jira, independent to the project selection on the homepage of the DevOps Portal. This is caused by the fact, that agile boards are not part of a Jira project, but instead are independent entities. We are striving to find a solution for the problem in a future version.

Released on November 09, 2023

PSA (Privacy and Security Assessment) Compliance

• The password reset procedure is now protected against automated use or misuse. After entering the email address, the user is now asked for his 2nd factor. This ensures, that it's not possible to spam users with password reset mails. Of course, it requires that 2FA has been enabled for the user. In general, it's recommend to enable 2FA for all your users. Therefore, 2FA has always been enabled by default when you create a new user on the DevOps Portal.

Enhancements

• Starting with Bitbucket 8.2, a new Create repository permission has been added by the vendor. This new permission is now granted to all users with a MASTER role. To enable it for existing projects, simply initiate a Resync of the project in the DevOps Portal. Please note, that users automatically get admin permissions in the repositories they create.
• In some tools (currently Jira, Confluence and Bitbucket) Project ADMINs can directly add individual users to their project choosing from one of the available roles or permissions. This is now cleaned-up when a Project Resync is initiated. To be more precise, a Project Resync removes any Project roles or permissions for users which don't have a role assigned in the DevOps portal.

Improvements

• Prepared the DevOps Portal for configuring tool specific project settings in the future.
• Updates of used software frameworks and libraries.
• When a Technical User is deleted, the sort order of the table is now preserved.

Bugfixes

• On the Projects page, assigning a role to a user which he already has, obviously has no effect. But unfortunately, after such an action the Assign button was disabled, even when another user was selected. This is fixed now.

Known Issues

• Unfortunately, the links to Agile Board and Backlog in the Jira tile of the DevOps Portal homepage do not work properly for users which have more than one project. In fact, the links will lead to the last visited agile board on Jira, independent to the project selection on the homepage of the DevOps Portal. This is caused by the fact, that agile boards are not part of a Jira project, but instead are independent entities. We are striving to find a solution for the problem in a future version.