Planning and Forecasting in Jira: Part 7

Roadmap Demo

Note: The recording has no sound. Please refer to the copy provided below.
Watch: https://youtu.be/9IKP1gDe-xU

demo-roadmap.png

The steps shown in the video are:

Now that there’s a Jira project and some sample issues, let’s review the basic roadmap. Go to the Jira project and click the “roadmap” link on the project’s left sidebar. Issues in the project are automatically shown here.

Use the options at the top of the page to filter issues by keyword, user, or status, and control the view.

There are also additional view settings at the bottom of the page.

From here you can create new epics, drag issues to reorder them and drag the colored bars to change start and end dates.

If dependencies exist, they are shown with a curved red line. To create a dependency, hover over one of the colored bars and drag the dots that appear to the applicable epic. Click on the red dependency line to see additional information like how issues are linked.

You can also use Jira’s standard “linked issues” feature and the dependency will automatically show in the roadmap.

Finally, click on an issue to view or edit its details.

Enable the Roadmap

board-configure.png

If you don’t see a roadmap link, the feature may be disabled. To enable it, go to the project’s board and click the ellipses on the top right. Then select “board settings” in the menu. You’ll need to be a board administrator to change board settings.

enable-roadmap.png

On the board settings page, click the “roadmap” link in the sub-menu and enable the feature using the toggle on the top right.

Part 8: Additional Planning Features in Confluence

1 comment

Vee KHONG
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 27, 2024

"Roadmap" link allows us to express, for example, that Epic-A blocks Epic-B. But it is curious that Jira does not present a visual representation along the time axis.  It is quite happy if we put B alongside A, ie, happening in parallel.  If Epic-B is blocked by Epic-A, then logically B should start after A is finished.  I look forward to hearing your input.

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events