Jira Agile Board Management Change
The existing feature and the reason for the change
When a project is created on Jira, Jira automatically creates a Scrum Board for the project, which is named by the project key. It was always possible, that the Project Admin later decides to have a Kanban board instead. To achieve this, the Project Admin can create a new agile board and delete the old one. Since the DevOps Portal automatically sets the Administrators of the board to match the Admins of the project, it's necessary for the DevOps Portal to find the correct board. Unfortunately, Jira doesn't maintain a connection between projects and boards. Therefore, the old algorithm was choosing the oldest board with a filter query on the project. But since all Jira users can create boards and in addition filter queries can be constructed, which reference multiple projects, it was possible to get into corner cases where the DevOps Portal was managing the Administrators of the wrong board. Therefore, the algorithm was changed. The filter query used by the board is no longer important. Instead, only the name of the board is relevant. The new algorithm even allows it keeping the Administrators of multiple boards in sync with the Admins of a project.
The enhanced feature
When a project is resynced or an Admin is added or removed from a project, the DevOps Portal will set the Administrators of the matching boards to the list of Project Admins. To qualify for a match, the board name has to start with the project key. For example, if the project key is "PKEY":
- Board names like "PKEY", "PKEY Kanban Board", "PKEY_Team_Board", "PKEY-CoolBoard" etc. will have their Administrators managed by the DevOps Portal
- Board names like "_PKEY MyBoard" or "Joe's Board" don't have a "PKEY" prefix. They will not be managed by the DevOps Portal.
Required actions on your side
- If nobody manually created boards, you don't have to change anything, since "PKEY" is the default name of boards which are automatically created. So they will be still found and managed by the DevOps Portal as before.
- If anybody manually created boards, please check the names and rename as necessary to get the desired behavior.
- Since board Administrators can rename their boards, all of them can decide themselves by eventually renaming the board, if they want to keep a Team board managed by the DevOps Portal or if they want to have an independent board, where the list of Administrators is manually maintained in Jira.
Enhancements
- It's now possible to assign the agent-admin role to Jenkins tech users using the checkbox "Allow to administer agents"
For more details see Connecting Inbound Jenkins Agents. - The REST API was extended and now supports all required management operations for projects. This contains CREATION/POST, PATCH, RETIRE and REACTIVATE as well as DELETE.
Improvements
- If a user is set to be a component lead of one or more components in a Jira project, these assignments are automatically removed when the role of the user is removed. Therefore, if you use component leads in your project, check if some components have no longer a lead, after you removed the role of a user.
- Switched to new translation mechanism of messages in the portal.
- Added documentation for XWiki.
Bugfixes
- When Jira was added to an existing project, it was not possible to select a non-default Workflow Scheme, Issue Type Scheme or Issue Type Screen Scheme.
- Manual language selection on the login screen did work properly only with the keyboard, but not using the mouse.