Minor changes are by default collapsed in the page history.
No changes
The page does not exist yet.
Failed to load changes
Version by on
Leave Collaboration
Are you sure you want to leave the realtime collaboration and continue editing alone? The changes you save while editing alone will lead to merge conflicts with the changes auto-saved by the realtime editing session.
When a project is created in the Portal, it's now possible in the section for Jira settings to select customized, centrally managed Worflow Schemes. If "Default" is used, a new Workflow Scheme will be automatically created just like before. The benefit of centralized Workflow Schemes is, that more sophisticated Workflows can be used to standardize Jira project settings. See example screenshot below.
Technical Users can now be locked and unlocked like other Users. This includes that Technical Users now have to be locked first, before they can be deleted. This allows you to find out first, if a Technical User is really no longer used. If something stops working, you can simply unlock the user again instead of deleting it. The screenshot below shows the enhanced Actions menu.
Improvement
The setting "Automatically scan images on push" for the Trivy Security Scanner in Harbor is now automatically enabled when a project is saved or created.
The project description is now put into the folder description in Jenkins.
Users, which have selected German instead of English as their preferred language in the Portal, will now get also notification emails in German.
Updated from Spring Boot v2 to v3.
Security
When a freshly created user was locked, he could reactivate himself using a still valid invitation link. This has been changed. Invitation links are now getting immediately invalid, when the user was successfully activated. If the user does not set a new password instantly after activation, the forgotten password link can be used to set a password.
Bugfixes
The links to Agile Board and Backlog in the Jira tile of the DevOps Portal homepage did not work properly for users which have more than one project. This was caused by the fact, that agile boards are not part of a Jira project, but instead are independent entities. A new info service is now determining the best available Agile board and will link to it.
