The Jira Roadmap is a useful internal tool that employees can use to create new tasks for development review, add information to existing tasks, and view task progression. It also gives insight into development timelines and future projects. Please use this as a first resource when trying to gather information on tasks.
Note: This is an internal tool that should not be shared with customers. If you are using the estimated release dates to inform customers of timelines, be sure to keep in mind that these dates are approximate and subject to change.
Table of Contents
Understanding Roadmap Views
There are six main view when using the Jira Roadmap: New Items, Proposed Items, All Open Items, Usability & Stability, Active Bugs, and Integrations.
Note: Board style roadmaps are covered later in the article.
a. New Items - Any recently created task, with the most recently created tasks displaying at the top.
b. Proposed Items - Feature requests or enhancements that are being reviewed by the development team. The Planning Stage column in this view will indicate where the task is at in the review process.
c. All Open Items - A full list of all unreleased tasks.
d. Usability & Stability - All tasks related to the stability of the system.
e. Active Bugs - All current bug tasks.
f. Integrations - All tasks related to current and projected CoreBridge supported integrations.
Each view has a list of tasks that include columns for quick summaries, priority levels, statuses, estimated release ranges, insights, and comments.
Note: Some views may have additional columns.
Tip: You can use the Find an idea in this view search bar found in the top right corner to quickly search through the tasks listed.
g. Summary - This will show in the column as a quick summary, or title, of the task. Clicking the summary name will open a side panel where you can view an overview, make comments, add insights, and see a general history of the task. Comments are where you can ask questions related to the task. Insights is where you can include new reports or requests from customers related to the task.
Note: You can also use the eye icon located at the top right to add yourself as a watcher on the ticket to receive notifications about its progression.
h. Priority - How important it is for the task to be completed. This helps development determine which tasks need to be completed in which order. If a priority level has been selected, it will either show as low, medium, high, or urgent.
i. Status - As a task progresses, there are statuses assigned to indicate where it is at in its lifecycle. You can click About this view on any page to get more information on how the statuses work for each view.
The statuses include:
The statuses listed below are in the relative lifecycle order of an idea.
To Do Statuses: Tasks that are identified but not yet started.
Discovery Statuses: The phase where research and exploration take place to define the idea.
Design Statuses: The phase for planning and creating design solutions.
Architecture Statuses: Focusing on the technical framework and structure required to support the idea.
Development Statuses: The development preparation work post design and architecture, followed by the active building and coding phase where the idea is being developed.
QA Statuses: Quality assurance testing to ensure the product meets standards.
Completed Statuses: The final stage where the idea is fully developed, tested, and ready for release.
j. Est. Release - The estimated release date range for the task.
Note: This is an approximated range that is subject to change.
k. Insights - Clicking on an insight will bring up the same side panel as clicking the summary, but with the insights tab selected. This is where any additional reports or requests from customers that are related, or the same, as the task can be entered. The most recently created insight will show at the top.
Note: A blue number indicates that there are insights you have not yet viewed.
l. Comments - Clicking on a comment will bring up the same side panel as clicking a summary or insight, but with the comments tab selected. This is where any questions related to the task can be answered, or where additional information about the task can be entered. The most recently created comment will show at the top.
Note: A blue number indicates that there are insights you have not yet viewed.
Understanding Roadmap Boards
Roadmaps allow you to view all tasks in a board style. Eventually, the Internal Release Planning and External Product Roadmap will be used to track and organize release timelines.
For now, the main roadmap view is Internal Roadmap.
All tasks are shown as cards that display a percentage of completion, associated development and company goals, priority level, and estimated start and release dates when applicable.
The cards are organized into month to month columns, showing you when the task is estimated to be released.
Clicking on a card will open a side panel where overview information, comments, insights, and task history can be found.
Creating a New Task
When a new bug or feature request needs to be submitted to development, you can create a new task using the Jira Roadmap.
1. Navigate to the New Items view.
2. Click Create, located at the top of the screen.
3. Fill in all relevant information to the bug or feature request using the provided template.
Note: Any links to a customer or test system should be the exact URL of where the bug or feature is in the system.
4. Select a Type from the following options:
- Bug: Something is broken and doesn't work as expected.
- Feature Request: Something new a user wants that doesn't exist yet.
- Enhancement: Improving something that already exists to make it better.
- Task: A to-do item that isn’t directly related to bugs or features but still needs to get done.
Note: This is an important step to ensure that the task gets added to the correct views.
You can additionally select:
- Priority - How important it is for the task to be completed. This is subject to change after development review.
- Customer segments - Whether the system(s) reporting is an independent or franchise system, as well as which franchise system(s).
- Following - Who, to your knowledge, is or will be involved in watching or maintaining the task.
Note: The reporter dropdown will automatically populate with the user who is creating the task and cannot be changed.
5. Select Create idea at the bottom right of the new task popup.
