Issues are the core building blocks of your plan. You can import issues from issue sources as covered on the Plans page, or you can create new issues directly in your plan then save them to your project.
Bear in mind that Advanced Roadmaps is a sandbox environment. Any changes made here, including creating or removing issues, won’t affect your Jira Software data unless you tell Advanced Roadmaps to save your changes to Jira.
Create a new issue
To add a new issue:
Navigate to +Create issue at the top of the Scope column.
Select the type of issue (epic, story, subtask) you want to create. If your plan contains more than one project, use the dropdown to select which project to assign the new issue.
Name your new issue, and choose a project if you’re making an epic. Select the checkmark to save.
Add other issue details in the fields displayed on your timeline such as assignee, team, estimate, sprint, release, and dates. The details you can specify for an issue will depend on your issue sources and how your plan is configured.
Advanced Roadmaps will place your new issue at the bottom of your current project. If you’ve made a child-level issue (such as a story or subtask), it will be listed under the collapsible x issues without parent heading at the bottom of your timeline until it’s linked to a parent task.
Insert a new issue
Alternatively, if you know where you’d like to add a new issue, you can tell Advanced Roadmaps where to create a new issue relative to another. This is handy for inserting epics at specific places in projects, or creating a child issue that inherits details from its parent task. On your timeline, hover over the desired destination issue, select themenu, then follow the same steps listed above.
If you insert an epic into your plan using this method, it will be automatically placed in the corresponding project. You can change this using the dropdown menu before selecting the checkmark to save it.
If you create a child issue, it will be nested underneath the parent ticket and inherit its sprints, releases, and teams values.
Link issue to a parent
To create a relationship between two issues, drag and drop a child into its parent issue in the Scope section. You can only link an issue to a parent of the corresponding hierarchy level that you've configured for your plan.
Jira Software admins may be familiar with an issue’s Resolution field. This field is set when an issue is moved from the “In Progress” to “Done” status, after which Jira Software considers the issue complete. This behavior is automatically configured as part of default workflows. However, if a custom workflow is used, the behavior needs to be manually configured as a post function. Learn more about Jira Software’s Resolution field and configuring post functions.
Advanced Roadmaps refers to a different field — the Status category change date — to define completed issues. By referring to this field, Advanced Roadmaps ensures a consistent approach between default and custom workflows. This change was recently implemented specifically to address issues without a set Resolution field being excluded from users' plans. You can find more detail about this on the Missing issues page.
Learn how to adjust the number of completed issues in your plan on the Configure plan settings page.
How you can schedule issues depends on how your teams are set up, and how you’ve configured your instance. For example, hierarchy configurations, estimation units, and custom dates all need to be configured before they can be used to schedule issues in your plan.
To learn the different ways that you can schedule issues in your plan, see Schedule issues.
Remove issues from your plan
There are two ways to remove issues from your plan in Advanced Roadmaps. The first way is to select the checkboxes of the issues you want to remove, then navigate to the Bulk actions menu > Remove from plan.
Unsaved issues can also be removed using the Review changes modal. Select the issues you want to remove, then select Discard selected changes to remove them from your plan.
Regardless of how you choose to do it, issues that have been saved to Jira won’t be affected when you remove them from your plan.