Non-Admin Permissions

Topics

Introduction

Release Management App has embedded functionality for cross-project components management. And in the future .. mapping components to versions creating so-called Component Versions.

This includes Classic Components (former Components bound to Projects). And in the future will include Atlassian Compass Components that are cross-project by definition and that are already integrated to track dependencies for Versions and Packages.

Why?

We believe Compass is the future for managing distributed architecture ecosystem (Components Management) through there are a number of Enterprises that are using Classic Components for time being and migration process will take decent time. So, we are here to help and let clients ease the process of cross-project components management.

Components

Cross-project components management is available on Components tab.

Open

Here you can find

• a list of cross-project components created

• their associated projects

• component lead

• default assignee

• custom labels

• and free-text/HTML description

Once created appropriate properties are propagated into each and every project.

Creating new cross-project components

Click on Create component button to create new cross-project component.

Open

You would need to specify all the same properties above.

To create components in multiple projects you should list all the projects you want to use in Projects lookup. You can choose from list of projects you associated with your Release Management Board in Board Settings.

Synching cross-project components

There’s a chance that components in different projects will get out of sync. This could happen if

• smb will edit component directly in Jira

• or use any other App for component management

To sync components across the projects click Synchronize components button. This will propagate the properties defined in Release Management to all the projects.

Deleting cross-project components

Click button on the right to delete cross-project component. This will cause deletion of corresponding component on Release Management Board + all the associated projects.

Explore cross-project components

By clicking on cross-project components you can explore and edit the details.

In particular, on Summary tab you can change:

• Component Name

• Description

• Add/remove projects

• component lead

• default assignee

• custom labels

You can also get an oversight of component scope - Jira issue associated with this Component from all the selected projects.

By clicking on the Scope view you can oversight Scope in detail. The screen should be familiar to you from version/package details screen. Thus you can:

• see a complete list of issues associated

• use set of predefined filters to shortlist the view

• full text search + JQL filters

• ability to assign existing Jira issues to Component

• create new issues and assign to Component

• view issues in Issue Navigator

• Switch between Custom/Default views

• Turn on Code feature.

If you have a huge scope and large number of columns you can always Zoom -in/-out the Component Details dialog.

What’s next?

We are adamant to create component version for our Release Management App whether it will be connected to Classic Components or Atlassian Compass Components.

We would love to hear from you if you believe this is a good idea and how you envisage such functionality and for what use case.