Questions about Basic roadmap + Advance roadmap

[Oranit]

1. Is there a possibility to add a task that is not in the projects scope and not included in Jira?  Such as - sales / pre sales activities etc, (Tasks not regarding to developments and product design activity...) ?

2. Can we set a baseline plan and check it during progress in front of the actual timeline and hours spent? (for example, in Instagantt there is a possibility to mark a plan as the baseline and always compare the current situation to the baseline to see all differences and  diviations)?

If there is such option:

2.1 Where can I find the instructions of how to work with that? 

2.2 How many 'baselines' can I set per project / sprint?

3. Is there a possibility to share a specific roadmap with client without giving him any access to any other info in the project?

[Michael Andolfatto · Accepted solution]

Hi @Oranit ,

I'll need some clarification for some of your questions but will provide initial responses:

> Is there a possibility to add a task that is not in the projects scope and not included in Jira?  Such as - sales / pre sales activities etc, (Tasks not regarding to developments and product design activity...) ?

Yes absolutely, but it depends on your project structure and personal definition of a task. Options here include:

1. Having a custom issue type in your development/design project designated for "general tasks" that gets pulled in from the issue source tied to your project

2. Having a separate Jira project/board that tracks tasks and pulling it in via an Advanced Roadmaps issue source

3. Creating issues directly in the Advanced Roadmaps interface (if what you mean by "not included in Jira" means actually not having a real issue created) will create a "conceptual" issue that does not really exist until data is pushed back from AR into Jira.

---

> Can we set a baseline plan and check it during progress in front of the actual timeline and hours spent? (for example, in Instagantt there is a possibility to mark a plan as the baseline and always compare the current situation to the baseline to see all differences and  diviations)?

You definitely won't have baselines to the same degree of functionality in Advanced Roadmaps unfortunately, but you can create multiple scenarios in a plan that provide similar functionality.

Creating a scenario (can make unlimited scenarios) clones your AR plan at its current point of time. Making changes in one plan do not affect a separate scenario. Where it falls short is that any changes made to Jira data directly will still affect the plan and all scenarios immediately.

---

> Is there a possibility to share a specific roadmap with client without giving him any access to any other info in the project?

You can share read-only copies of plans if you would like to ensure that all they see is what is presented on the Timeline view. Otherwise if they have Jira access, you can provide them the ability to enter the plan while restricting the Jira project's permission.

[Oranit]

Hello Michael

Your answers have been very helpful.

The last question I have is if there is a possibility to work with the roadmap (weather basic or advance) with all types of Jira tickets or only with the epics?

We sometimes manage a board with tasks and bugs and not with user storys and epics, 

If we set the time planned for the tasks, is it possible to trackthem as a timeline in the roadmap?

Many thanks for your help 

Oranit.

[Michael Andolfatto]

Hey @Oranit , glad to hear it helped.

Yes, both the basic and advanced roadmaps will allow you to work with multiple issue types. By default, Jira's hierarchy level is as follows:

Epic-level (largest)

Story-level (middle- includes most other issue types such as Tasks, Bugs, or custom ones)

Sub-task-level (smallest)

With Advanced Roadmaps, you can create additional hierarchy levels above the Epic-level, but either roadmapping tool will allow you to view things like Tasks and Bugs as long as they are defined in the scope of the plan.