---
title: "Create a Forecast with Advanced Setup"
canonical: "https://support.55degrees.se/space/SP/4457201665/Create%20a%20Forecast%20with%20Advanced%20Setup"
format: markdown
---
### What is the Advanced Setup?

While our **Forecast Templates** give you a *simple* way to make reliable group forecasts without starting from scratch, some users may want full control over all options - thus create their forecast using the Advanced Setup.

The following is a step-by-step guide on how to create a Group Forecast in Portfolio Forecaster, using the Advanced Setup. 

> ℹ️ Before you run your Group Forecast, make sure you understand the difference between *what you’re forecasting* and *what drives the forecast.* A small mistake here can lead to misleading results. Here's how to get it right: [here](https://55degrees.atlassian.net/wiki/spaces/SPP/pages/3964862834/Create+a+Forecast#What-to-think-about-when-creating-the-forecast%3F).

> ℹ️ Missing Versions? They were not supported during our initial release, but we hope to add them back soon!

### Creating a Forecast with the Advanced Setup

To create a new Group Forecast with the Advanced Setup, click the ‘Create’ dropdown  in the Navigation Bar and select ‘Group Forecast’.

#### Step 1 - Defining Forecast

The first section is about defining what you would like to forecast. 

![Screenshot 2025-12-03 at 14.34.58.png](media://9466195c-fc0d-4cc1-8d5e-237cf2f55d5e)


> ℹ️ The most common approach is to pick one item type. However, there are use cases in which a user may pick multiple item types to forecast. For example, if items were brought in from another space and a different item type was used in place of epics there, then users would need to include that item type as well.


> ℹ️ Read more on how to use JQL filters in Portfolio Forecaster [here](https://55degrees.atlassian.net/wiki/spaces/SPP/pages/3964864540).

---

#### Step 2 - Remaining Work

The second section is about defining what constitutes “remaining work” for your forecasted items.

![Screenshot 2024-10-15 at 16.03.45.png](media://5bb6fd17-3403-4f7a-8e71-6cf2ef49607e)


---

### Step 3 - Historical Data

After you select [SUBMIT] , your forecast will be run, and you will be taken to your newly created forecast. 🥳 

---

### What to think about when creating the forecast?

![Screenshot 2025-07-30 at 10.06.20.png](media://42417f85-03a7-497c-90b5-9f67598b641f)

> ℹ️ As long as your “parent” has “children,” you can choose any item type, for example: Initiative (parent) > Epics (children)

> ℹ️ You are free to use any item links to create the hierarchy. By default, we’ll use the standard parent field; use the one that matches your setup and context.

---

### Warning and Error Messages

You’ve created your configuration but instead of generating a forecast, you get the following error message:


> 📝 Sometimes, the forecast you are trying to make does not yet have enough historical data because it is too new. What you can do is to use children from a completely different spaces, (but who seem to be roughly similar to your current project) to see what could happen. This can be done in Step 3 by using the JQL feature. You should only do this in extreme cases and until you have enough historical data in your current project.