Release Dependencies

Overview

The idea of Release Dependencies is to bring classical

  • start to start

  • start to finish

  • finish to start

  • finish to finish

dependency types to all the views in Release Management Apps.

There are also 2 angles of it, namely:

  • Visualize to create observability and drive decisions, also different color coding for better visibility and customizations.

  • Automation, in particular scheduling, aligning, alerting, etc.

Dependencies on Roadmap

As of now (Aug '23) we started with MVP version of Release Dependencies - outline dependencies on Roadmap view.

To turn on dependencies click on appropriate toggle on the bar.

When the toggle is on you will see all dependencies depicted and direction of dependency (dependency type)

When the toggle is on you can also create new dependencies. To do so put a mouse to any version/package you want to “link“ with other. You will see 2 anchors at a start and finish.

Click on it (anchor), drag to dependent version/package

If you bring it to start of dependent version the App will suggest to create “smth to start“ dependency

If you bring it to finish of dependent version the App will suggest to create “smth to finish“ dependency

Drop it to create dependency.

To delete dependency click on it to see appropriate suggestion

Click on it to confirm the deletion.

Reminder: All the above works only if Dependencies toggle is turned on.

Dependencies on Board view

To turn on dependencies on board view click on appropriate toggle.

Once selected all the dependencies between versions will be showed up.

Compared to Roadmap view when we show absolutely all dependencies including links between versions and packages … Board view only includes links between versions. We did it in order not to complicate the view.

In case of dependency could not be vitalized - dependent Fix Versions, Cross-Project Version, Epic, Sprint or JQL Version removed from board or shortlisted - you will see a visual indication about existing dependency.

By clicking on it you will see the list of dependencies

To create new dependency click on the anchors indicating “start to ..“ and “finish to ..“ dependencies, drag and drop to dependent version.

While dragging to dependent item the App will suggest you two pods indicating “ .. to start” and “.. to finish“ dependency.

To see dependency details you can click on it and appropriate dialog will be show with list of dependencies

From this dialog you can remove dependency if you want by clicking Delete

Dependencies on Listview

List view is Excel-like or Microsoft Project-like representation of releases and dependencies. To turn dependencies on select appropriate toggle

Once you selected 2 addition columns will be shown to outline list of releases that current one depends on, and list of releases depends on current one.

Both are editable. By clicking on it you can add/remove dependencies - that are versions or packages.

Your feedback?

As always, please reach out to our support outlining your priorities with this feature and the use case you would like to cover. We appreciate it and take it in consideration when making our priorities.