---
language: "en"
---
# Easy Agile Programs
## Easy Agile Programs
Empowering remote, distributed and co-located teams to make and execute cross-team plans, right in Jira.
### [Purchasing \& Administration](https://help.easyagile.com/easy-agile-programs/purchasing-administration.md)
#### [Get Started: Set up Easy Agile Programs](https://help.easyagile.com/easy-agile-programs/get-started-set-up-easy-agile-programs.md)
#### [How-To Guides](https://help.easyagile.com/easy-agile-programs/how-to-guides.md)
#### [Help \& Support](https://help.easyagile.com/easy-agile-programs/help-support.md)
---
language: "en"
---
# Beyond Essential SAFe
Easy Agile Programs is used by a number of Enterprise level organisations operating beyond Essential SAFe.
Currently our app, provides a holistic view of the features and dependencies for an Agile Release Train rather than providing a view across multiple value streams.
In order to achieve a portfolio view we recommend:
* using a [dedicated board](https://help.easyagile.com/easy-agile-programs/create-a-program.md#Choosing-your-Program-Roadmap-configuration) for your features so you have access to the Quick Filters from this board. You can then create and use Quick Filters to focus in on a specific portfolio epic, initiative or capability when scheduling issues, during team planning sessions or ART syncs
* using [option 3 'I want to schedule other issue types from a dedicated agile board onto my Program Roadmap'](https://help.easyagile.com/easy-agile-programs/create-a-program.md#Choosing-your-Program-Roadmap-configuration) when creating your Program so that you can schedule and visualise portfolio epics, initiatives and/or capabilities on the roadmap. These higher level initiatives won't be positioned above your features however you will be able to see them within the Program.
We're currently looking at ways to improve the experience of our app for larger SAFe implementations. If you have any feedback or suggestions [please reach out to us.](https://arijea.atlassian.net/servicedesk/customer/portal/2/group/2/create/30)
---
language: "en"
---
# Compatibility & Performance
## App performance and scalability
Some of our happy enterprise customers include Bosch, JP Morgan, BMW, Oracle, IBM and Coca Cola.
Easy Agile Programs is fully supported by our Product and Engineering team and in active development. We are committed to growing and developing the capabilities of our team to ensure a scalable, performant product today and into the future.
## Is Easy Agile Programs compatible with team-managed (previously next-gen) projects?
Yes. Team-managed projects can be added to a new or existing Program.
Functionality may be limited by your Program configuration. For more information, please read our page on [compatibility for team-managed projects.](https://help.easyagile.com/easy-agile-programs/team-managed-projects-next-gen.md)
## Jira compatibility
For compatibility with [Jira Data Center 10](https://confluence.atlassian.com/jirasoftware/jira-software-10-0-x-release-notes-1416825224.html), update to Easy Agile Programs v8.0.0+.
Please check the [Versions page on the Atlassian Marketplace](https://marketplace.atlassian.com/apps/1219491/easy-agile-programs-pi-planning-program-board-dependencies/version-history) for details on supported versions of Jira for each Easy Agile Programs version.
While we endeavour to maintain support for commonly used versions of Jira, we will no longer support old versions of Jira that are [not supported by Atlassian](https://confluence.atlassian.com/support/atlassian-support-end-of-life-policy-201851003.html).
## Easy Agile Programs Browser Support
Easy Agile products support the same set of browsers as Jira. We test our apps on Chrome, Edge, Safari and Firefox.
### Internet Explorer 11
Microsoft released Edge in 2015 to replace Internet Explorer. Since then Internet Explorer has not received major updates or support for modern standards. [Microsoft discourage the use of Internet Explorer as the default browser.](https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/The-perils-of-using-Internet-Explorer-as-your-default-browser/ba-p/331732)
Atlassian announced that they would be [retiring support for Internet Explorer](https://blog.developer.atlassian.com/retiring-ie11-support-for-atlassian-cloud-server-and-data-center-products/?utm_medium=docs&utm_source=easy-agile-user-story-maps&utm_campaign=compatability) in September 2019. Support for Internet Explorer on Cloud was discontinued in March 2020, and on Jira Data Center and Jira Server from version 8.6 onward.
As a small team it's becoming increasingly difficult to support browsers that are no longer supported by Atlassian, as such new features added to Programs version 3.2.0 and onwards will not be available in Internet Explorer.
We will continue to support the existing feature set in Internet Explorer 11 until Jira 8.6 enterprise support ends in October 2021 but we encourage you to switch to a modern browser for the best experience.
---
language: "en"
---
# Confidence Voting
Confidence voting is available:
* On Jira Cloud (i.e. Jira sites with "....atlassian.net" in the URL) on all pages of the app
* In Data Center version 6.0.0+; [a Jira Administrator can install the latest version](https://confluence.atlassian.com/upm/updating-apps-273875710.html).
The Confidence vote tool is available in the top right-hand corner of the [**Program board**](https://help.easyagile.com/easy-agile-programs/program-board.md) and [**Team planning**](https://help.easyagile.com/easy-agile-programs/team-planning-board.md) pages.
## What is Confidence voting?
Here's a summary of confidence voting from
> Once ART PI Risks have been addressed, teams vote on their confidence in meeting their team PI objectives.
>
> Each team conducts a vote using their fingers (fist of five) or a digital tool for remote events.
>
> If the average is three fingers or above, then management should accept the commitment. If it's less than three, the team reworks its plan.
>
> Anyone voting two fingers or fewer should be allowed to voice their concerns. These concerns might add to the risk list, require replanning, or provide information. Once each team has voted, it's repeated for the entire ART, with everyone expressing their confidence in the collective plan.
## Confidence votes in Easy Agile Programs
The Confidence vote tool is available in the top right-hand corner of the [**Program board**](https://help.easyagile.com/easy-agile-programs/program-board.md) and [**Team planning**](https://help.easyagile.com/easy-agile-programs/team-planning-board.md) pages.
Each person in the team can easily register their vote by selecting one of the icons from the dialog.
If you wish to change your vote, simply click on a different score. To remove your vote, click on your original vote to cancel the selection.
Currently all voting is anonymous.
To make it easier to engage your team, we've added a sharable link. Click "Share with team" then paste the link in your preferred team communications channel. When a team member uses this link, it will automatically open the confidence vote dialog on your team planning board or program board.
 Do you have any feedback on this feature? [Reach out to our product team to let us know what you think!](https://arijea.atlassian.net/servicedesk/customer/portal/2/group/2/create/30?customfield_11100)
---
language: "en"
---
# Configuring dependencies for a Program
Dependencies are used to visualize and track issue links in Easy Agile Programs.
* [Dependency lines are shown on most pages of the app](https://help.easyagile.com/easy-agile-programs/dependencies.md).
* [The Reports page summarizes dependencies for an Increment](https://help.easyagile.com/easy-agile-programs/dependencies-reports.md).
## Choose dependency link type for a new Program
When [creating a Program](https://help.easyagile.com/easy-agile-programs/create-a-program.md), you can choose the main issue link type from Jira to use for dependencies. This is the last step in the 6-step process. This can be changed later.3
The dropdown will show all issue link types available on your Jira site. This will include Jira's default issue link types and any custom issue link types. See Atlassian's guide *Configure issue linking* [for Jira Cloud](https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-linking/) or [for Jira Data Center](https://confluence.atlassian.com/adminjiraserver/configuring-issue-linking-938847862.html).
* Easy Agile Programs will use the "blocks" / "is blocked by" link type by default, if it is available.
You can only select one issue link type for a Program. Other Programs can use a different issue link type.
[Users can select other link types from Jira to show in the "Dependencies" dropdown](https://help.easyagile.com/easy-agile-programs/dependencies.md#How-many-dependency/link-types-will-show?):
* on Jira Cloud (i.e. Jira sites with "....atlassian.net" in the URL)
* on Jira Data Center with app version 7.2.0+
The link type configured for the Program will be on by default for all users.
Note: A Jira Administrator can disable issue linking for the whole Jira site. This means issue links won't be visible at all in Jira or Easy Agile Programs.
### Flip directions of dependency link type
Use "Flip directions of dependency link type" in Edit Program if the link health colors shown in Easy Agile Programs don't match the link text. This setting only changes the visualization in the app, not the issue link data in Jira.
For example, say Issue 1 needs to be done before Issue 2.
|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| An issue link in Jira says that Issue 1 **blocks** Issue 2. |  |
|  If Issue 1 is scheduled first, the dependency link between them *should* be **green**: they're in the correct order. |  |
|  If issues scheduled in the *correct* order show a **red** dependency line, **use "Flip directions of dependency link type" to fix this**. |  |
This setting will *not* change which order dependencies are created in ["Create dependencies" mode on the **Team Planning** page](https://help.easyagile.com/easy-agile-programs/dependencies.md#Creating-dependencies-between-team-level-issues-in-Easy-Agile-Programs).
## Edit dependency link type
Use the "[Edit program](https://help.easyagile.com/easy-agile-programs/create-a-program.md#CreateandeditaProgram-EditaProgram)" button in the top right of the [**Program roadmap** page](https://help.easyagile.com/easy-agile-programs/program-roadmap.md) to edit the settings for an existing Program.
The "Dependency link type" settings are at the bottom of this form.
## What permissions are required to create or edit dependencies?
To create new issue links, you'll need the "Link Issues" permission. If the issues you want to link are from different Jira projects, you'll need this permission for both projects.
If you don't have permission to create issue links in Jira, you'll see an error when trying to create dependencies in Easy Agile Programs.
A Jira Administrator can update these permissions by editing the Permissions Scheme for the project(s). See Atlassian's guide [for Jira Cloud](https://support.atlassian.com/jira-cloud-administration/docs/manage-project-permissions/) or [for Jira Data Center](https://confluence.atlassian.com/adminjiraserver/managing-project-permissions-938847145.html).
---
language: "en"
---
# Configuring Jira for Easy Agile Programs
Easy Agile Programs is designed to integrate with your existing Jira data.
We've prepared this guide to make it easy to identify any changes you might need to make in order for set-up to run smoothly.
## What is a "Program" made of?
A **Program**is a single view of work across multiple teams or boards from Jira. This lets you plan and track work for a team-of-teams (or Release Train) and work together towards shared goals.
A Program will have:
* A roadmap, split into a series of **Increments** . Each Incrementis a series of Sprints.
* A set of **Teams**. Each team is a Scrum or Kanban board from Jira.
[*Learn more about how you'll navigate Programs, Increments and Teams in the app*](https://help.easyagile.com/easy-agile-programs/the-anatomy-of-easy-agile-programs.md)*.*
## What do you need to have in Jira before you create a Program?
To create your first [Program](https://help.easyagile.com/easy-agile-programs/create-a-program.md) and the first [Increment](https://help.easyagile.com/easy-agile-programs/create-and-edit-a-program-increment.md) in it, you'll need to have:
1. [One Jira board for each team](https://help.easyagile.com/easy-agile-programs/what-is-a-team-in-easy-agile-programs-configuring-.md)
2. A set of issues to build the [roadmap](https://help.easyagile.com/easy-agile-programs/schedule-features-epics-into-your-increment.md): either the Epics from your team boards, or one dedicated Jira board with all roadmap issues
3. (Optional) A Jira board for [issues *above* Epics](https://help.easyagile.com/easy-agile-programs/third-level-hierarchy.md)
4. (Optional) A pair of [start date and end date fields to sync roadmap issue schedules](https://help.easyagile.com/easy-agile-programs/date-syncing-with-native-jira-date-fields.md)
5. A link type to use for [Dependencies](https://help.easyagile.com/easy-agile-programs/configuring-dependencies-for-a-program.md) by default (in new versions of the app, users can also enable other link types)
For more detail on configuring each of these, read on!
## Hierarchy in Easy Agile Programs
You can visualize up to 3 levels of issues in Easy Agile Programs:
* (Optional) [Higher-level](https://help.easyagile.com/easy-agile-programs/third-level-hierarchy.md) issues, e.g. Initiatives
* [Roadmap](https://help.easyagile.com/easy-agile-programs/configuring-the-roadmap-issue-source.md)-level issues, e.g. Epics or Features
* [Team](https://help.easyagile.com/easy-agile-programs/what-is-a-team-in-easy-agile-programs-configuring-.md)-level issues, e.g. Stories, Tasks, etc.
### 
Team boards
Each team in the Program will need one **Jira board**.
* Issues from this board can be scheduled from the board's backlog on the [**Team planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md).
* Scrum teams can sync Sprints and Estimates from their Jira board with Easy Agile Programs.
If you use a **Jira** **project** for each team, you'll want to use the "main" or default Jira board for that Project. By default, new Projects have a single-project board with a simple board filter query `project IN (ABC) ORDER BY Rank ASC`.
[Learn more about team boards in Easy Agile Programs](https://help.easyagile.com/easy-agile-programs/what-is-a-team-in-easy-agile-programs-configuring-.md).
**Can I change it later?**
Yes: you can add or remove team boards from a Program at any time.
You can change what issues are in a team board at any time by editing the **Board filter query** in Jira.
### Roadmap issues (e.g. Epics, Features)
[The roadmap in Easy Agile Programs](https://help.easyagile.com/easy-agile-programs/schedule-features-epics-into-your-increment.md) will be made of Jira issues.
* By default, these will be Epics from Jira.
* Sometimes this issue type is renamed "Features".
[You'll need to select a **Roadmap issue source** when creating your Program](https://help.easyagile.com/easy-agile-programs/configuring-the-roadmap-issue-source.md). This will be EITHER:
1. Epic-level issues from your team boards OR
2. One Jira board for all your roadmap issues
* You can change what issues are in this board at any time by editing the **Board filter query** in Jira. You can also switch to a different Jira board.
* To make the order of issues sync between Easy Agile Programs and the Jira board, enable Ranking in Jira board configuration.
* Quick Filters from that board will be available in Easy Agile Programs.
The Epic issue type and other issue types
Epics are a special issue type: [they're part of the default hierarchy](https://www.atlassian.com/software/jira/guides/issues/overview#what-is-jira-issue-hierarchy). In many versions of Jira, Epics are the only issue type that can be "parent of" a standard-level issue like a Story or Task.
**Renamed the "Epic" issue type?**
If the Epic issue type has been *renamed*, Easy Agile Programs will still detect and use it the same way.
**Not using Epics?**
If you're using a new or different issue type to build your Roadmap, you'll need to select "Any issue types from a dedicated board" as your *Roadmap issue source* when creating a Program.
Since this can't use the default Epic-child relationship, you'll need to also specific a hierarchy link or link type that connects your roadmap issues to their team issues.
If you enable **date syncing**, date fields on your roadmap issues will be used and updated when making plans in Easy Agile Programs.
This means you'll be able to see and edit the same timeline in other tools such as [Plans for Jira Cloud Premium](https://support.atlassian.com/jira-software-cloud/docs/what-is-advanced-roadmaps/) or [Advanced Roadmaps for Jira Data Center](https://confluence.atlassian.com/jirasoftwareserver/discover-advanced-roadmaps-for-jira-1044784153.html).
**Can I change it later?**
You *can't* swap the *Roadmap issue source* later (e.g. from "Epics from team boards" to "Epics from a dedicated board"). You'll need to create a new Program to change the source type.
If you're using a dedicated board, you *can* change to a different board.
### Higher-level initiatives (optional)
You can visualize a set of issues representing higher-level business initiatives on the [**Program board** page](https://help.easyagile.com/easy-agile-programs/program-board.md). These will be the level *above* Epics/Features.
To use this, you'll need:
1. All the higher-level issues for this Program in one Jira board
2. Standardized start and end date fields (see below)
3. A link type that connects the roadmap issues (e.g. Epics or Features) to your higher-level issues
* If you've used [Jira Cloud Premium](https://support.atlassian.com/jira-cloud-administration/docs/configure-the-issue-type-hierarchy/) or [Advanced Roadmaps for Jira Data Center](https://confluence.atlassian.com/jirasoftwareserver/configure-your-jira-software-instance-for-advanced-roadmaps-1044784156.html#ConfigureyourJiraSoftwareinstanceforAdvancedRoadmaps-CustomHierarchyLevelsARJ) to configure issue hierarchy above Epics, you can use the "**Parent link**" connection from that hierarchy.
* You can also use any default or custom **link type** from [Jira Cloud](https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-linking/) or [Jira Data Center](https://confluence.atlassian.com/adminjiraserver/configuring-issue-linking-938847862.html).
Easy Agile Programs will show higher-level issues from this Jira board when the dates on the issues overlap with the period of the Increment. Clicking a higher-level issue will filter the page to only show children of that issue, based on the link type configured.
[Learn more about higher-level initiatives in Easy Agile Programs](https://help.easyagile.com/easy-agile-programs/third-level-hierarchy.md).
**Can I change it later?**
Yes: you can add, change or remove the higher-level issue configuration at any time.
## Standardized fields
### 1 link type for Dependencies
Easy Agile Programs uses **issue links** from Jira to represent dependencies. The app will use these issue links to [show dependency lines](https://help.easyagile.com/easy-agile-programs/dependencies.md) and [generate reports](https://help.easyagile.com/easy-agile-programs/dependencies-reports.md).
Each Program is configured with one main **link type** from Jira. By default, the app uses "blocks" / "is blocked by". [Learn more about configuring dependencies](https://help.easyagile.com/easy-agile-programs/configuring-dependencies-for-a-program.md).
[Users can select other link types from Jira to show in the "Dependencies" dropdown](https://help.easyagile.com/easy-agile-programs/dependencies.md#How-many-dependency/link-types-will-show?):
* on Jira Cloud (i.e. Jira sites with "....atlassian.net" in the URL)
* on Jira Data Center with app version 7.3.0+
The link type configured for the Program will be on by default for all users.
. Jira Administrators can activate issue linking on [Jira Cloud](https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-linking/) or [Jira Data Center](https://confluence.atlassian.com/adminjiraserver/configuring-issue-linking-938847862.html)
**Can I change it later?**
Yes: you can swap the link type used for a Program at any time.
### Standardized start and end date fields for date sync (optional)
If you enable **date syncing** , date fields on your [roadmap issues](https://help.easyagile.com/easy-agile-programs/schedule-features-epics-into-your-increment.md) will be used and updated when making plans in Easy Agile Programs. This means you'll be able to see and edit the same timeline in other tools such as [Plans for Jira Cloud Premium](https://support.atlassian.com/jira-software-cloud/docs/what-is-advanced-roadmaps/) or [Advanced Roadmaps for Jira Data Center](https://confluence.atlassian.com/jirasoftwareserver/discover-advanced-roadmaps-for-jira-1044784153.html).
To use date syncing, you'll need:
1. One start date field and one end date field for the dates on all roadmap-level issues in the Program
2. Both fields are on the Issue Screen(s) used for these issues / Jira projects, so that users can edit the fields
If you *don't* use date fields, [schedule issues manually on the roadmap using drag-and-drop](https://help.easyagile.com/easy-agile-programs/scheduling-issues-from-the-roadmap-backlog.md). Schedules will be stored in a hidden property on the issue.
[Learn more about date syncing](https://help.easyagile.com/easy-agile-programs/date-syncing-with-native-jira-date-fields.md).
**Can I change it later?**
Yes: you can add, change or remove the date fields used for a Program at any time.
## Integrating with existing planned work
### Can I start using Easy Agile Programs mid-Increment?
Yes: you can create a new Increment that starts before today.
* You'll be able to [add your existing plans to the roadmap using date sync or drag-and-drop](https://help.easyagile.com/easy-agile-programs/schedule-features-epics-into-your-increment.md#Editing-the-roadmap).
* Existing sprints from Scrum boards can be synced to the Increment, and will show the work that was planned/completed during that time.
* In older versions of the app, completed sprints do not always appear when selecting sprints to sync. We recommend updating the app before creating a new Increment with dates in the past.
* Kanban teams will *not* be able to schedule team-level issues on dates in the past; they will only be able to schedule future work or roadmap-level issues.
### Can I use my existing plans from Jira's Plans / Advanced Roadmaps?
Yes: Easy Agile Programs will work with existing plans made in [Plans for Jira Cloud Premium](https://support.atlassian.com/jira-software-cloud/docs/what-is-advanced-roadmaps/) or [Advanced Roadmaps for Jira Data Center](https://confluence.atlassian.com/jirasoftwareserver/discover-advanced-roadmaps-for-jira-1044784153.html). This is because the tools will visualize the same issues from Jira.
To best synchronize with Plans / Advanced Roadmaps:
* When configuring date syncing in Easy Agile Programs, select the same start date and end date fields that are used in Plans / Advanced Roadmaps.
* If you have an additional level of hierarchy above the Epic issue type, configure Higher-level initiatives by selecting the "Parent Link" link type to use this hierarchy.
## Next steps
* Explore an existing Program on our sandbox demo site at [demo.easyagile.com](http://demo.easyagile.com).
* On this site, you'll have [**Manage Programs** permission](https://help.easyagile.com/easy-agile-programs/permissions.md#The%25E2%2580%259CManagePrograms%25E2%2580%259Dpermission). This will allow you to see and edit the configuration of Programs and Increments, and create new ones.
* You'll also be able to explore the Jira boards and issues that are used in these Programs to see how they fit together.
* [Install a free evaluation of Easy Agile Programs on your Jira site from the Atlassian Marketplace](https://marketplace.atlassian.com/apps/1219491/easy-agile-programs-pi-planning-program-board-dependencies/?tab=overview).
* Grant [**Manage Programs** permission](https://help.easyagile.com/easy-agile-programs/permissions.md#The%25E2%2580%259CManagePrograms%25E2%2580%259Dpermission) to yourself or someone else so that you can [create a Program](https://help.easyagile.com/easy-agile-programs/create-a-program.md).
*** ** * ** ***
If you have more questions about configuring Jira and Easy Agile Programs, [reach out to our support team here](https://arijea.atlassian.net/servicedesk/customer/portal/2/group/2/create/30)!
---
language: "en"
---
# Configuring sprint sync for an Increment
## Selecting a sprint source for an Increment
When [creating an Increment](https://help.easyagile.com/easy-agile-programs/create-and-edit-a-program-increment.md), you'll choose from two *Sprint source* options:
* Teams independently manage their own sprints on their team board
* Teams use shared sprints from a dedicated board
You **can't** swap the source type after creating an Increment! If you've selected the wrong type, you'll need to delete the Increment and create a new one.
You **can:**
* Swap which sprints you're using from the selected source.
* Swap to a different Jira board if you're using a shared sprint board.
| | **Shared sprints** | **Teams manage their own sprints** |
| **Goal** | Centralise sprint management on one board. This can be useful for cross-team reporting, such as with sprint reports in Jira. | Allow teams to autonomously manage their sprints, just like on their backlog in Jira. |
| **Configuration** | Select a Jira board and a set of sprints from that board. All teams will schedule issues into those sprints when planning in Easy Agile Programs. | Each scrum team will choose which sprints to use for an Increment. The "Sync sprints" form will show on the [**Team planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md) until sprints for that team are selected. |
| **Changing sprints** | Change sprints, or switch to a different source board, in the Edit Increment menu. | Swap a sprint for another on that board on the [**Team planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md). |
| **Effect for kanban teams** | Scheduling an issue in a sprint column on the [**Team planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md) will update the sprint on the issue in Jira. However, this field may not be visible on the issue view in Jira Cloud, based on the [Issue screen configured in Jira](https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-screens/). | [Kanban team boards](https://help.easyagile.com/easy-agile-programs/kanban-boards.md) won't use sprints; issues can be scheduled in columns to align with other teams' work and the features on the roadmap. |
|-----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
## Selecting and changing sprints from Jira
Choose sprints from your source Jira board: either the team's board, or the selected source board shared for the whole Increment.
* You *can't* choose sprints that are already syncing with another Increment or Program.
* You can select *Closed* sprints, which can be used if the Increment you're creating in the app is already in progress for your teams.
**You can choose to let Easy Agile Programs create new future sprints for an Increment.**
* These sprints will be created on the selected sprint source or team board in Jira.
* Sprints will be named after the Increment: "\[Increment name\] - Sprint #", e.g. "Increment 1 - Sprint 1". Rename a sprint from the Backlog page in [Jira Cloud](https://support.atlassian.com/jira-software-cloud/docs/edit-a-sprint-in-a-company-managed-project/) or [Jira Data Center](https://confluence.atlassian.com/jirasoftwareserver/planning-sprints-938845427.html).
### Team-managed sprints
If you've created an increment using "Teams independently manage their own sprints on their team board", the "Sync sprints" form will show on the [**Team planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md) for each team until sprints are selected.
**We recommend selecting sprints for each team soon after creating an Increment** . This sets your teams up with the right sprints, before the broader team needs to use the [**Team planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md).
You can't select sprints that weren't *created on* this Jira board when first syncing sprints, although they will show in the Jira Backlog when issues on this board are in those sprints. See *"About sharing sprints between Jira boards"* below.
However, these sprints can be selected later when changing synced sprints. To use sprints created on other Jira boards:
1. Add or create a placeholder sprint(s) when first syncing sprints.
2. Then, swap the placeholder sprint for the desired sprint from another Jira board.
|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| If sprints for this Increment haven't yet been selected for a team, the "Sync your Jira sprints" screen will show when opening that [**Team planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md). |  |
| Swap out one sprint for another with the ✏️ "Edit" button. Hover over the sprint name to see this. If this button doesn't show when hovering your mouse cursor over the sprint name, this Increment is configured to use shared sprints. A can change sprints from the "Edit Increment" form. |   |
If sprints have been synced but one or more of the selected sprints have then been deleted from Jira, you'll be asked to select sprints again.
### Shared sprints
When creating a new Increment and selecting the Sprint source "Teams use shared sprints from a dedicated board", you'll be asked to select sprints immediately.
|-------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Choose sprints from the selected board when creating a new Increment. |  |
| Edit the source board or selected sprints from the [Edit Increment](https://help.easyagile.com/easy-agile-programs/create-and-edit-a-program-increment.md#Editing-an-increment) menu. |  |
## What does sprint syncing provide?
Easy Agile Programs will sync the *team-level* planned issues for the sprints:
* Issues added to the sprint in Jira will appear in that sprint column in Easy Agile Programs.
* Adding an issue to the sprint in Programs will add it to that sprint in Jira and update the sprint field.
### Limitations
We don't recommend using the same sprints across more than one Program. The ["Program" and "Program Increment" custom fields](https://help.easyagile.com/easy-agile-programs/programs-custom-fields.md) will not correctly show information from both Programs.
**All teams in an Increment will need to be on the same sprint cadence.** [The Scaled Agile Framework (SAFe) recommends this synchronized cadence to facilitate cross-team coordination](https://scaledagileframework.com/apply-cadence-synchronize-with-cross-domain-planning/).
* Sprints in an Increment don't need to be the same length on Cloud (sites with "....atlassian.net" in the URL), and v6.0.0+ on Data Center. When creating or editing an Increment, select Sprint length "Custom" to set a length in weeks for each sprint separately.
**Easy Agile Programs does not sync sprint dates**. Dates shown in Programs are calculated based on the Increment start date and the sprint lengths, so they may not match the dates on the sprint in Jira. The app will not add dates to future sprints that do not have dates in Jira.
**Sprint names are only shown on the** [**Team planning page**](https://help.easyagile.com/easy-agile-programs/team-planning-board.md). Even if all teams in an Increment are sharing sprints, sprint names are not shown on the [**Program board** page](https://help.easyagile.com/easy-agile-programs/program-board.md).
**Issues on the roadmap can't be planned in sprints.** These issues can be scheduled across multiple sprints. The schedule of roadmap-level issues can be [synced with date fields on the issues in Jira](https://help.easyagile.com/easy-agile-programs/date-syncing-with-native-jira-date-fields.md).
Want more functionality from sprints in Easy Agile Programs? [Let us know](https://arijea.atlassian.net/servicedesk/customer/portal/2/group/2/create/332?summary=More+functionality+for+sprints+in+Easy+Agile+Programs)!
## About sharing sprints between Jira boards
**Every sprint has an origin board** where they were created. Sprints will always show on the board they're created on, even if the sprint is empty.
* When a board is deleted from Jira, the sprints from that board are not automatically deleted.
* When selecting a sprint in Jira (e.g. in a search or when editing the sprint field on an issue), most dropdown lists will show the origin board name.
**You can schedule issues in a sprint from another board** . When one or more of a board's issues appear in another sprint, **that sprint will appear on this Jira board too**. You'll see it on the Backlog page with future sprints, on the Active Sprint page, or with completed sprints in Reports.
### Sharing sprints using Easy Agile Programs
When you're using shared sprints in an Increment in Easy Agile Programs, sprints from the selected board will show on the [**Team planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md).
This lets teams easily add issues to these sprints, even if they're from another Jira board. After at least one issue is scheduled in each sprint, the sprints will then show on the team's backlog in Jira.
## Next: planning team work with sprints
Teams can plan their work using sprints on the [**Team planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md) in Easy Agile Programs (or in the backlog in Jira).
[Set a capacity for each sprint in story points and use estimates to plan at a sustainable pace](https://help.easyagile.com/easy-agile-programs/estimations.md#Sprint-capacity).
Teams can learn more about using the configured sprints on [Scrum and sprints](https://help.easyagile.com/easy-agile-programs/sprints.md)*.*
---
language: "en"
---
# Configuring the Roadmap issue source
This guide helps you choose which of the 3 *Roadmap issue source* options will work best for your situation.
Configuring this correctly when creating a Program will let you [add the epics/features you need to your roadmap](https://help.easyagile.com/easy-agile-programs/schedule-features-epics-into-your-increment.md).
This selection *cannot* be changed later when editing a Program
## How the roadmap is used
The *Roadmap issue source* determines what issues will show in the [Roadmap backlog](https://help.easyagile.com/easy-agile-programs/scheduling-issues-from-the-roadmap-backlog.md) for you to schedule on your roadmap.
**What belongs on the Roadmap?** Roadmap-level plans are typically:
* Bigger than a single sprint
* Sometimes across multiple teams
* Of interest to other teams or stakeholders
### Automatic roadmap scheduling with date syncing
If you also configure [date syncing](https://help.easyagile.com/easy-agile-programs/date-syncing-with-native-jira-date-fields.md) for your Program, issues from this source will be *automatically* scheduled on the roadmap.
Issues scheduled in different Programs, or in Plans for Jira / Advanced Roadmaps, will show on the same dates everywhere you view them.
### Where the Roadmap is displayed
You'll see issues from the Roadmap across multiple pages of the Easy Agile Programs app:
* All the issues on the [**Program roadmap** page](https://help.easyagile.com/easy-agile-programs/program-roadmap.md)
* Issues in **purple** on the [**Program board** page](https://help.easyagile.com/easy-agile-programs/program-board.md)
* Issues in **purple** on the [**Team planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md)
* The Team Planning page will only show roadmap issues scheduled in that team's swimlane or the "Shared team features" swimlane.
### Seeing the relationship between roadmap-level and team-level issues
On the [**Program board** page](https://help.easyagile.com/easy-agile-programs/program-board.md), click a purple roadmap issue to show that issue's children.
Use this to see which teams are contributing to shared features.
Similarly, click a purple roadmap issue on the [**Team planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md) to show that issue's children.
* If you open the "Backlog" panel first, issues in that panel will be filtered by the roadmap issue too!
If you select a *Roadmap issue source* that uses epic-level issues, this will show the *child* issues of that issue using [Jira's inbuilt hierarchy](https://www.atlassian.com/software/jira/guides/issues/overview#what-is-jira-issue-hierarchy).
If you select "Any issue types from a dedicated board", you'll select an issue link type from Jira for this relationship.
### Can I add issues to the roadmap for more than one Program?
Yes, you can schedule an issue in more than one Program if it's in the *Roadmap issue source* for both Programs.
## Choosing the *Roadmap issue source* for your situation
You **can't** change the *Roadmap issue source* after you've created a Program. You'll need to create a new Program to use a different *Roadmap issue source*.
You **can**change:
* Change the set of team boards included in a Program
* Swap from one dedicated roadmap board to a different board
* Change the link connecting roadmap issues to team-level issues, if you're not using epics
To choose the right option for your situation, you'll need to know 2 things:
1. If you'll use issues from the **teams' Jira boards** , or centrally manage the roadmap with a **dedicated Jira board**
| **Teams' Jira boards** | **Dedicated Jira board** |
|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| * Use the epics that your teams use on their boards. * Epics added with [date syncing](https://help.easyagile.com/easy-agile-programs/date-syncing-with-native-jira-date-fields.md) automatically added to their team's swimlane on the roadmap (instead of "Shared team features"). * No Quick Filters available in Easy Agile Programs to filter the roadmap. | * Use an existing board, or create a new one that includes all the issues you want on your roadmap. * Control what's included on the roadmap and roadmap backlog by editing the board filter query. * Use Quick Filters from that Jira board to filter roadmap-level issues in Easy Agile Programs. * Reorder issues using Easy Agile Programs if your board has Ranking enabled. |
2. If you'll schedule **Jira epics** , or **other issue types** on the roadmap
| **Jira epics** | **Any issue types** |
|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|
| * Use the default epic issue type (even if it's been renamed on your Jira site). * Use the inbuilt epic-to-child hierarchy to connect epics on the roadmap to team-level issues. | * Use a custom issue type or multiple issue types. * Configure how these issues on the roadmap will connect to team-level issues. |
On Jira Cloud Premium, use all epic-level issues in your [issue type hierarchy](https://support.atlassian.com/jira-cloud-administration/docs/configure-the-issue-type-hierarchy/) by choosing "Epic level issues from my team boards" or "Epic level issues from a dedicated board".
You'll then choose one of these *Roadmap issue source* options in Step 3 of creating a Program:
| | **Option** | **Roadmap backlog source** | **Issue type** |
|---|---------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|-----------------|
| 1 | [**Jira epics from my team boards**](https://help.easyagile.com/easy-agile-programs/configuring-the-roadmap-issue-source.md#Jira-epics-from-my-team-boards) | Team board backlogs | Epics only |
| 2 | [**Jira epics from a dedicated board**](https://help.easyagile.com/easy-agile-programs/configuring-the-roadmap-issue-source.md#Jira-epics-from-a-dedicated-board) | Dedicated Jira board | Epics only |
| 3 | [**Any issue types from a dedicated board**](https://help.easyagile.com/easy-agile-programs/configuring-the-roadmap-issue-source.md#Any-issue-types-from-a-dedicated-board) | Dedicated Jira board | All issue types |
## Configuring the options
Select a roadmap issue source in Step 3 when [creating a new Program](https://help.easyagile.com/easy-agile-programs/create-a-program.md#Create-a-new-Program).
### Jira epics from my team boards
This option suits situations where each team is responsible for managing epics on their own backlog and adds their plans to the Program roadmap.
Details
Effects:
* The roadmap backlog will only be epics (even if you've renamed this issue type).
* The epic-to-child hierarchy will connect epics on the roadmap to team-level issues. This is the "Parent link" field on Jira Cloud, or "Epic link" field on Jira Data Center.
* You will *not* be able to use Quick Filters in Easy Agile Programs to filter epics.
* (Jira Cloud Premium only) All issue types configured at level 1 in your [issue type hierarchy](https://support.atlassian.com/jira-cloud-administration/docs/configure-the-issue-type-hierarchy/) will be available when using this option.
### Jira epics from a dedicated board
This option suits situations where the roadmap is centrally managed. The Roadmap backlog will include Epics from a single Jira board.
Details
You'll select this Jira board when creating a Program, but you can also switch the roadmap board later.
* If you don't have an existing Jira board for this, you may need to create a new one in Jira first.
* You can use a multi-project board.
Effects:
* The roadmap backlog will only be epics (even if you've renamed this issue type).
* The epic-to-child hierarchy will connect epics on the roadmap to team-level issues. This is the "Parent link" field on Jira Cloud, or "Epic link" field on Jira Data Center.
* Use Quick Filters from that Jira board to filter epics.
* Change what issues are included on the Roadmap by editing the board filter query in Jira.
* (Jira Cloud Premium only) All issue types configured at level 1 in your [issue type hierarchy](https://support.atlassian.com/jira-cloud-administration/docs/configure-the-issue-type-hierarchy/) will be available when using this option.
### Any issue types from a dedicated board
This is the most flexible option and suits Programs in any of the following situations:
* The inbuilt epic issue type isn't used
* The roadmap needs to include multiple issue types
Details
You'll select this Jira board when creating a Program, but you can also switch the roadmap board later.
* If you don't have an existing Jira board for this, you may need to create a new one in Jira first.
* You can use a multi-project board.
You'll also need to select a link type to describe how team issues to roadmap issues. You can change this later. This is because Easy Agile Programs can't automatically use the epic-to-child relationship when you're not using epics.
* If your custom hierarchy is configured in Jira (e.g. [in Jira Cloud Premium/Enterprise](https://support.atlassian.com/jira-cloud-administration/docs/configure-the-issue-type-hierarchy/) or [with Advanced Roadmaps in Jira Data Center](https://confluence.atlassian.com/jirasoftwareserver/configure-your-jira-software-instance-1044784156.html#ConfigureyourJiraSoftwareinstanceforAdvancedRoadmaps-CustomHierarchyLevelsARJ)), select "Parent" to use this hierarchy.
Effects:
* All issue types (other than sub-tasks) will show in the Roadmap backlog
* Use Quick Filters from that Jira board to filter roadmap-level issues.
* Change what issues are included on the Roadmap by editing the board filter query in Jira.
You can't schedule an issue on the Edit roadmap page if that issue is *already scheduled* on a Team planning page.
This *Roadmap issue source* makes it possible for the same issues to appear in the Team planning page backlog AND the Roadmap backlog.
## Example configurations
### Simplest option: epics from teams
Say you've added three team boards to your Program: WEB board, IOS board, and ADR board. Each team already manages the epics/features they're working towards on their own backlog.
If you select "Jira epics from my team boards", the Roadmap backlog will contain: epics from the WEB board + epics from the IOS board + epics from the ADR board.
### Existing feature backlog of epics
Say your backlog of epics is already managed on a board called "Feature backlog". You'd like to use these epics to build your cross-team roadmap.
Use "Jira epics from a dedicated board" and select this board when creating or editing a Program.
### Epics from teams, but with Quick Filters
Say you'd like to use the Epics from your team boards, but you'd also like to use Quick Filters in Easy Agile Programs.
Your team boards use Jira projects WEB, IOS, and ADR. Create a new Jira board to manage the backlog that includes those three projects: this will have a board filter query like `project IN (WEB, IOS, ADR) ORDER BY Rank ASC`. Create new Quick Filters on that board in Jira.
Use "Jira epics from a dedicated board" and select this board when creating or editing a Program.
### Integrating with a custom hierarchy in Jira's Plans / Advanced Roadmaps
Say you're using a custom hierarchy in Jira using [Plans on Jira Cloud](https://support.atlassian.com/jira-cloud-administration/docs/configure-the-issue-type-hierarchy/) or [Advanced Roadmaps on Jira Data Center](https://confluence.atlassian.com/jirasoftwareserver/configure-your-jira-software-instance-1044784156.html#ConfigureyourJiraSoftwareinstanceforAdvancedRoadmaps-CustomHierarchyLevelsARJ). The configuration uses a custom issue type named "Features" that is one level above stories. You haven't renamed the inbuilt Epic issue type for this.
To use this custom issue type, you'll need to use "Any issue types from a dedicated board" the the link type "Parent".
If you don't have an existing board containing all the Features, you'll need to create a new one in Jira. This might mean creating a new Filter (or saved search) that includes all the required Features; then, you can create a new board based on that Filter.
### Custom issue types, without custom hierarchy
If you're using Jira Cloud Standard, it isn't possible to change the [default hierarchy in Jira](https://www.atlassian.com/software/jira/guides/issues/overview#what-is-jira-issue-hierarchy). You may also choose this if your Jira site isn't configured with the hierarchy you'd like to use in your Program.
Say you'd like to use two custom issue types on the roadmap: "Features" and "Enablers". Your teams create these issues in their projects (WEB, IOS, and ADR).
If you don't have a hierarchy configured in Jira, you'll need to use issue links instead. A Jira Administrator can create a custom issue link type created on your Jira site. This could be named "implements / is implemented by". For example, five Tasks on the team board *implement* a Feature on the roadmap.
Create a new Jira board that includes the projects WEB, IOS, and ADR. To avoid scheduling other issue types on your roadmap and make it easier to find the issues you need, edit the board filter to include only these two issue types. This results in a board filter like: `project IN (WEB, IOS, ADR) AND issuetype IN (Feature, Enabler) ORDER BY Rank ASC`.
Use "Any issue types from a dedicated board". Select this new board when creating or editing a Program, and the link type "implements".
## Learn more about configuring boards in Jira
| **Jira Cloud** (URL contains ....atlassian.net) | **Jira Data Center** |
|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Creating a board: * [Create a Scrum board based on Projects](https://support.atlassian.com/jira-software-cloud/docs/create-a-board/) * [Create a board based on filters](https://support.atlassian.com/jira-software-cloud/docs/create-a-board-based-on-filters/) * [Example JQL queries for board filters](https://support.atlassian.com/jira-software-cloud/docs/example-jql-queries-for-board-filters/) [Edit a board filter on a company-managed board](https://support.atlassian.com/jira-software-cloud/docs/edit-a-board-filter-on-a-company-managed-board/) | [Creating a board](https://confluence.atlassian.com/jirasoftwareserver/creating-a-board-938845220.html) [Editing a board's filter](https://confluence.atlassian.com/jirasoftwareserver/configuring-filters-938845268.html#Configuringfilters-Editingaboard%27sfilter) |
| [Configure Quick Filters](https://support.atlassian.com/jira-software-cloud/docs/configure-quick-filters/) | [Configuring Quick Filters](https://confluence.atlassian.com/jirasoftwareserver/configuring-quick-filters-938845301.html) |
| [Add, edit, and delete an issue type](https://support.atlassian.com/jira-cloud-administration/docs/add-edit-and-delete-an-issue-type/) | [Defining issue type field values](https://confluence.atlassian.com/adminjiraserver/defining-issue-type-field-values-938847087.html) |
| [Configure issue linking](https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-linking/) | [Configuring issue linking](https://confluence.atlassian.com/adminjiraserver/configuring-issue-linking-938847862.html) |
## Next steps: using the roadmap
* [Create an Increment](https://help.easyagile.com/easy-agile-programs/create-and-edit-a-program-increment.md) to plan items during a period on the roadmap
* Use [date syncing](https://help.easyagile.com/easy-agile-programs/date-syncing-with-native-jira-date-fields.md) to automatically add issues to the roadmap
* Grant [**Manage Programs** permission](https://help.easyagile.com/easy-agile-programs/permissions.md#The%25E2%2580%259CManagePrograms%25E2%2580%259Dpermission) to let contributors access the "Edit Roadmap" page to drag and drop issues onto the roadmap
*** ** * ** ***
## Easy Agile support
If you're having issues creating or configuring a Program, [reach out to our support team here](https://arijea.atlassian.net/servicedesk/customer/portal/2/group/2/create/30?summary=Help+with+Roadmap+issue+source)! We can answer any questions, walk you through the process, and help you find a configuration that works for you.
---
language: "en"
---
# Create and edit a Program
To start using Easy Agile Programs, you'll need to create a Program.
A Program (or called an Agile Release Train) is a group of teams working together towards a shared goal or roadmap. [Teams in Easy Agile Programs are represented by Jira boards](https://help.easyagile.com/easy-agile-programs/what-is-a-team-in-easy-agile-programs-configuring-.md).
## Create a new Program
Users with [**Manage Programs** permission](https://help.easyagile.com/easy-agile-programs/permissions.md#The%25E2%2580%259CManagePrograms%25E2%2580%259Dpermission) can create a new Program from the [**Program list** page](https://help.easyagile.com/easy-agile-programs/program-list.md).
[*Learn how to find the Easy Agile Programs app in Jira*](https://help.easyagile.com/easy-agile-programs/navigate-to-your-program.md).
In the latest version of Easy Agile Programs, you'll see the following six-step process. This includes the Cloud app, and app versions 5.3.0+ on Data Center.
*If you're using Easy Agile Programs v5.2.1 or earlier on Jira Data Center, you'll see a one-page form instead of this six-step process.* [*Find instructions for the older Create Program form here*](https://help.easyagile.com/easy-agile-programs/create-program-on-v5-2-1-and-earlier.md)*.*
The create program workflow is a six-step process:
### 1. Name your program
Enter a name for your Program. This can be changed later.
The Program name will also show in the ["Program" custom field](https://help.easyagile.com/easy-agile-programs/programs-custom-fields.md) on issues scheduled in Program.
### 2. Add your teams
Add a board from Jira for each team who'll work in this program.
You can choose any Scrum, Kanban or team-managed board, including boards already used in other programs.
For more info on team boards, see: [What is a "team" in Easy Agile Programs? Configuring Jira Boards](https://help.easyagile.com/easy-agile-programs/what-is-a-team-in-easy-agile-programs-configuring-.md)
### 3. Choose issues for your roadmap with the *Roadmap issue source*
You can choose to build your roadmap using epics from the selected team boards.
Alternatively, manage the roadmap using a dedicated Jira board. The board filter query will determine what issues are used in Easy Agile Programs.
**You cannot change this selection after creating the Program.** You *can* switch which Jira boards are used.
See [Configuring the Roadmap issue source](https://help.easyagile.com/easy-agile-programs/configuring-the-roadmap-issue-source.md) for guidance on finding the right option for your situation.
**On Jira Cloud Premium only** , epics now include all epic-level (level 1) issues from your [issue type hierarchy](https://support.atlassian.com/jira-cloud-administration/docs/configure-the-issue-type-hierarchy/).
### 4. Configure third level hierarchy (optional)
Connect your teams with higher level business initiatives (i.e. capabilities) by adding an additional level of hierarchy to your program.
Select the board that contains your third level issues. You may need to create a new board in Jira that contains the issues you wish to display.
Select the Jira link type that connects your features (e.g. Jira epics) with the third level issues.
This step is optional. For more details, [Third level hierarchy](https://help.easyagile.com/easy-agile-programs/third-level-hierarchy.md).
### 5. Configure date syncing (optional)
Keep your features (and third level hierarchy issues) in sync with Jira by selecting the start and end date fields used.
This will allow for real time integration between Easy Agile Programs, Jira and Advanced Roadmaps so there's less manual work to keep everything up to date.
For date syncing to work correctly, the date fields selected must be shown on the Jira edit issue screen. This is something your Jira Administrator can help you with.
For more details, see [Date syncing with native Jira date fields](https://arijea.atlassian.net/wiki/pages/createpage.action?spaceKey=EAPD&title=Date%20syncing%20with%20native%20Jira%20date%20fields&linkCreation=true&fromPageId=1933869180)
*This step is mandatory when using third level hierarchy (step 4).*
### 6. Choose a dependency link type
Use the dropdown to select the dependency link type you want to visualise on your program.
[Learn more about dependency configuration](https://help.easyagile.com/easy-agile-programs/configuring-dependencies-for-a-program.md).
Once you've created your Program, you'll be taken to the new Program to [create your first Increment.](https://help.easyagile.com/easy-agile-programs/create-and-edit-a-program-increment.md)
## Edit a Program
Users with [**Manage Programs** permission](https://help.easyagile.com/easy-agile-programs/permissions.md#The%25E2%2580%259CManagePrograms%25E2%2580%259Dpermission) can edit their Program from the [**Program roadmap** page](https://help.easyagile.com/easy-agile-programs/program-roadmap.md).
In this menu, you can:
* Edit the Program Name.
* If you edit the Program Name, the [Program custom field](https://help.easyagile.com/easy-agile-programs/programs-custom-fields.md) will also reflect this change.
* Add or remove [team boards](https://help.easyagile.com/easy-agile-programs/what-is-a-team-in-easy-agile-programs-configuring-.md) from the Program.
* If you're using a dedicated board for your [*Roadmap issue source*](https://help.easyagile.com/easy-agile-programs/configuring-the-roadmap-issue-source.md), change the board.
* Add or change a [third level hierarchy](https://help.easyagile.com/easy-agile-programs/third-level-hierarchy.md) board.
* Enable or change [date syncing](https://arijea.atlassian.net/wiki/pages/createpage.action?spaceKey=EAPD&title=Date%20syncing%20with%20native%20Jira%20date%20fields&linkCreation=true&fromPageId=1933869180) at the for tighter integration with Jira
* Change the [dependency link type visualised on the Program](https://help.easyagile.com/easy-agile-programs/configuring-dependencies-for-a-program.md).
## Delete a Program
You need Jira Administrator permission to delete a Program. Find the "Delete program" option on a Program on the Program list page:
As an extra safeguard, you will be required to enter the program name into the dialog to confirm the delete action.
On Data Center app versions v5.2.1 or earlier, users with [**Manage Programs** permission](https://help.easyagile.com/easy-agile-programs/permissions.md#The%25E2%2580%259CManagePrograms%25E2%2580%259Dpermission) can also delete a Program.
*** ** * ** ***
## Easy Agile support
If you're having issues creating or configuring a Program, [reach out to our support team here](https://arijea.atlassian.net/servicedesk/customer/portal/2/group/2/create/30?summary=Help+with+Program+config)! We can answer any questions, walk you through the process, and help you find a configuration that works for you.
---
language: "en"
---
# Create and edit a Program Increment
A Program Increment is a time-boxed period, often a quarter, to deliver planned customer value.
Every Increment in Easy Agile Programs is made of a series of sprints from Jira. This means teams use the same sprints when planning, whether they're using the [**Team planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md) in Easy Agile Programs, or the Backlog in Jira.
Users with [**Manage Programs** permission](https://help.easyagile.com/easy-agile-programs/permissions.md#The%25E2%2580%259CManagePrograms%25E2%2580%259Dpermission) can create, edit, and delete Increments from the [**Program Roadmap** page](https://help.easyagile.com/easy-agile-programs/program-roadmap.md).
## Create an Increment
Use the "Create Increment" button on the [**Program Roadmap** page](https://help.easyagile.com/easy-agile-programs/program-roadmap.md) to create a new Increment.
You'll need to configure:
1. The Increment Name
2. The Increment start date
3. The number/length of sprints
4. The sprint source
### Sprint management
When creating or editing an Increment, you'll set the number of sprints (from 3 to 12) and the sprint length (1-4 weeks each).
This will also be used to calculate the end date of the Increment.
*Any of these settings can be changed later.*
**All teams in a Program will need to use the same sprint cadence**: starting and ending sprints at the same time.
You can now customise the length of each sprint in an Increment separately.
This allows the Increment to better adapt for planning periods or holidays.
*Variable sprint lengths are available now on Cloud (sites with "....atlassian.net" in the URL), or v6.0.0+ of the app on Jira Data Center.*
### Sprint source
The Sprint source cannot be changed after creating an Increment.
The sprints for an Increment can be either:
* One set of sprints **shared** by all teams in an Increment
* A set of sprints for **each team**
[**Check this guide to find which option will work best for you**](https://help.easyagile.com/easy-agile-programs/configuring-sprint-sync-for-an-increment.md)**.**
### Date syncing
[In earlier versions of the app, date syncing was included Increment](https://help.easyagile.com/easy-agile-programs/date-syncing-on-v5-2-1-and-earlier.md)configuration. [Date syncing](https://help.easyagile.com/easy-agile-programs/date-syncing-with-native-jira-date-fields.md) is now managed at the [Program](https://help.easyagile.com/easy-agile-programs/create-a-program.md) level.
### After creating an Increment
Now that you've created an Increment, you're ready to [make plans on the roadmap](https://help.easyagile.com/easy-agile-programs/schedule-features-epics-into-your-increment.md).
## Edit an Increment
To edit an increment, click the (...) menu on the Increment and select "Edit Increment".
* This button will be missing if you do not have [**Manage Programs** permission](https://help.easyagile.com/easy-agile-programs/permissions.md#The%25E2%2580%259CManagePrograms%25E2%2580%259Dpermission).
From here you can:
* Change the Increment Name
* Changing the Increment name will automatically update the [custom fields](https://help.easyagile.com/easy-agile-programs/programs-custom-fields.md)
* Change the Increment start date
* Change the length and number of sprints in your increment
* If the Sprint source is "shared sprints from a dedicated board", swap the synchronized sprints or the source board
If you'd like more editing capabilities, [let us know your use case here](https://arijea.atlassian.net/servicedesk/customer/portal/2/group/2/create/332?summary=More+Increment+editing+options+in+Easy+Agile+Programs)!
## Delete an Increment
To delete an increment, click the (...) menu on the Increment and select "Delete Increment". This action is not reversible.
*** ** * ** ***
## FAQs
### Does every team in the Program have to follow the same cadence?
**Yes, all teams in a Program will need to use the same sprint cadence**: starting and ending sprints at the same time.
If you're teams run on different sprint cycles, we recommend grouping teams that share sprint cycles into separate Programs. This helps teams:
* **See dependencies:**
* Teams on the same cadence will see [dependencies as colored lines in the app](https://help.easyagile.com/easy-agile-programs/dependencies.md).
* Dependencies on teams *outside* the Program will be [displayed as an icon on affected issues](https://help.easyagile.com/easy-agile-programs/dependencies.md#Externaldependencies).
* **See the value of improving alignment:** by seeing how Easy Agile Programs uses aligned sprints to keep teams in sync, teams can decide if aligning sprints with a broader group of teams would suit them.
### Are sprint dates synced with Jira?
The dates shown in Easy Agile Programs are calculated based on the Increment start date, sprint count, and sprint lengths. These dates are currently not synced with Jira so it is possible to have conflicting dates between Easy Agile Programs and Jira.
---
language: "en"
---
# Customizing card layout
## Adding additional fields to issue cards
On the [**Team Planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md), you can add up to 3 additional fields to the issue cards. These fields will be configured for that Team and Program and visible for all users.
To configure additional fields:
1. Open "..." menu in the top right corner of the Team Planning page.
2. Select the "Card settings" option.
3. Add or remove any fields you'd like to see from your Jira issues.
## Visualizing Flags / impediments from Jira
**Flags in Easy Agile Programs are available:**
* on Jira Cloud (i.e. Jira sites with "....atlassian.net" in the URL)
* on Jira Data Center with [app version 6.0.0+](https://updates.easyagile.com/announcements/keeping-teams-aligned-in-easy-agile-programs). If you're on Jira DC and can't see this functionality, ask Jira Administrator to update the app!
When an issue is "Flagged" in Jira, the issue card shows as yellow in Jira: on the Backlog, Active Sprint, and/or Kanban board page.
Flagged issues will be highlighted the same way on the [**Program board**](https://help.easyagile.com/easy-agile-programs/program-board.md) and [**Team planning**](https://help.easyagile.com/easy-agile-programs/team-planning-board.md) pages. :
This is currently view-only in Easy Agile Programs. To add or remove the flag, you will need to open the issue in Jira. Learn more about Flagging an issue [in Jira Cloud](https://support.atlassian.com/jira-software-cloud/docs/flag-an-issue/) or [in Jira Data Center](https://confluence.atlassian.com/jirasoftwareserver/flagging-an-issue-938845533.html).
If you'd like to be able to add/remove the flag from within Easy Agile Programs, [please reach out to us via support](https://arijea.atlassian.net/servicedesk/customer/portal/2/group/2/create/30).
---
language: "en"
---
# Date syncing on v5.0.0-5.2.1
## How to configure date syncing
On the **Create/Edit Increment** screen:
* Select the **Start Date** and **End Date** field used
* By default, Start date/Due date will be selected on Cloud and Target start/Target end will be shown on Server/Data Center.
* Click on the **Create/Update Increment** button to save your changes.
**Confirm with your Jira Administrator that these date fields on the Jira edit issue screen.**
 Rescheduling issues in Easy Agile Programs will not automatically sync back with Jira unless the date fields are on this screen. More information on adding date fields to issue screens can be found in the [Atlassian's guide to Configuring issues](https://confluence.atlassian.com/adminjiraserver/configuring-issues-938847082.html).
Note: Editing an increment requires [**Manage Programs**](https://help.easyagile.com/easy-agile-programs/permissions.md#The%25E2%2580%259CManagePrograms%25E2%2580%259Dpermission) or **Jira Administrator** permissions.
## FAQs
### Can I continue without using date syncing?
Yes. Simply leave these fields blank when creating a new increment. Without date syncing, any scheduling changes made to your feature roadmap will not be reflected to the rest of Jira. Additionally, any scheduling changes to the feature made outside of Programs will *not* be automatically reflected on the **Program Roadmap**.
Please note: team level issues like user stories will be in sync with Jira for scrum boards without date syncing as we use the sprint to keep these issues updated.
### Will turning on date syncing impact previous increments?
No. Dates are added on the increment so that the plans for previous increments are not impacted.
Once date fields are selected on an increment, Programs will remember these dates and pre-populate your selection for the following increments.
If you would like to enable date syncing for a current or past increment, add the date fields on the edit increment modal.
---
language: "en"
---
# Configuring date syncing with Jira date fields
Date syncing provides closer integration between Easy Agile Programs, Jira, and other planning tools.
By using date fields on your Jira issues as the key data source, you can see the same plan anywhere that uses your Jira data, including:
* The [Timeline](https://www.atlassian.com/software/jira/guides/basic-roadmaps/overview) view in Jira Cloud projects
* [Plans for Jira Cloud Premium](https://support.atlassian.com/jira-software-cloud/docs/what-is-advanced-roadmaps/)
* [Advanced Roadmaps on Jira Data Center](https://confluence.atlassian.com/jirasoftwareserver/discover-advanced-roadmaps-for-jira-1044784153.html)
* Other [Atlassian Marketplace](https://marketplace.atlassian.com/) apps that use the same fields
Date syncing is available:
* on Jira Cloud (i.e. Jira sites with "....atlassian.net" in the URL)
* on Jira Data Center with app version 5.3.0+; [a Jira Administrator can install the latest version](https://confluence.atlassian.com/upm/updating-apps-273875710.html)
[On Data Center v5.0-5.2.1, date syncing could be configured for each Increment](https://help.easyagile.com/easy-agile-programs/date-syncing-on-v5-2-1-and-earlier.md).
## What does date syncing provide?
Date syncing can be used to manage:
* Issues on the [Roadmap for each Program Increment](https://help.easyagile.com/easy-agile-programs/schedule-features-epics-into-your-increment.md)
* [Third-level issues](https://help.easyagile.com/easy-agile-programs/third-level-hierarchy.md)
Date syncing isn't used for team-level plans. [Synchronize your teams' plans using sprints](https://help.easyagile.com/easy-agile-programs/configuring-sprint-sync-for-an-increment.md).
Date syncing provides a 2-way sync for issues in your [*Roadmap issue source*](https://help.easyagile.com/easy-agile-programs/configuring-the-roadmap-issue-source.md):
1. When issues have dates in Jira that *overlap* with an Increment, Easy Agile Programs will automatically display them in that Increment.
2. Updating issues on the [Edit roadmap](https://help.easyagile.com/easy-agile-programs/scheduling-issues-from-the-roadmap-backlog.md) page will also update the date fields in Jira.
[Click here for a visual walkthrough on how date syncing affects roadmap-level issues](https://easyagile.storylane.io/share/rghoqxyb8kro).
The ["Program" and "Program Increment" custom fields](https://help.easyagile.com/easy-agile-programs/programs-custom-fields.md) will also be synchronized for these issues when a user views the roadmap in Easy Agile Programs (on Cloud, and on Data Center v7.2.0+).
### Date syncing is optional
You can continue without date syncing by leaving the fields empty when you create/edit a Program.
You'll still be able to [schedule issues on the roadmap manually using drag-and-drop](https://help.easyagile.com/easy-agile-programs/scheduling-issues-from-the-roadmap-backlog.md).
* [Third-level hierarchy](https://help.easyagile.com/easy-agile-programs/third-level-hierarchy.md) cannot be used without configuring date syncing.
* Team-level plans will still be [synchronized with sprints](https://help.easyagile.com/easy-agile-programs/configuring-sprint-sync-for-an-increment.md).
## Configure date syncing
To sync date fields between Jira and Easy Agile Programs, you'll need:
1. The date fields editable on the issues in Jira.
2. The same date fields selected in the Program.
### Configuring date fields in Jira
**For Easy Agile Programs to read and update the date fields, the user must be able to edit the same data in Jira**. This means:
* The fields are visible on the issue when editing.
* The user has permission to edit them.
[Click here for a walkthrough on adding date fields to issues on Jira Cloud](https://easyagile.storylane.io/share/7jdajnon8u0a).
To make the fields visible on the issue, **a Jira Administrator needs to add them to the** ***(Issue) screen*** **in Jira**.
* Find the correct screen(s) by opening the Project settings and opening the "Screens" page.
* Check Atlassian's documentation on configuring screens in [Jira Cloud](https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-screens/) or [Jira Data Center](https://confluence.atlassian.com/adminjiraserver/defining-a-screen-938847288.html).
* [Learn more about how fields and screens work together in Jira](https://confluence.atlassian.com/adminjiraserver/project-screens-schemes-and-fields-938847220.html).
For [team-managed projects (Jira Cloud only)](https://support.atlassian.com/jira-software-cloud/docs/learn-the-basics-of-team-managed-projects/):
1. [Add a pair of *global* date fields to the team-managed project](https://confluence.atlassian.com/jirasoftwarecloud/customize-work-item-fields-in-team-managed-projects-951392551.html).
2. Add these fields to the layout for each work type.
Note:
* Different issue types and projects can use different screens. You may need to add the fields to multiple screens, depending on what issues are used on the roadmap.
* You can configure different screens for Create/Edit/View operations using a *Screen scheme* in [Jira Cloud](https://support.atlassian.com/jira-cloud-administration/docs/manage-screen-schemes/#Associating-a-screen-with-a-work-item-operation) and [Jira Data Center](https://confluence.atlassian.com/adminjiraserver/associating-a-screen-with-an-issue-operation-938847289.html). Add the fields to the *Edit*screen to enable Easy Agile Programs to sync dates.
* On Jira Cloud, Project Administrators can edit the [*layout*](https://support.atlassian.com/jira-software-cloud/docs/configure-field-layout-in-the-issue-view/) for issue types. However, this can only use fields that are already on the *screen*.
### Configuring date fields for a Program
Date syncing is configured when creating or editing a Program.
In step 5 when [creating a new Program](https://help.easyagile.com/easy-agile-programs/create-a-program.md).
In the "[Edit Program](https://help.easyagile.com/easy-agile-programs/create-a-program.md#Edit-a-Program)" menu.
* You can add, swap or remove date fields at any time.
* Changing the date fields will *not* immediately change the values of the new fields in Jira.
This configuration affects *all*Increments in your Program.
[On v5.0.0-5.2.1, date syncing was configured separately for each Increment.](https://help.easyagile.com/easy-agile-programs/date-syncing-on-v5-2-1-and-earlier.md)
### Disabling date syncing
To stop using date syncing, remove the selected fields from the dropdowns in the [Edit Program](https://help.easyagile.com/easy-agile-programs/create-a-program.md#Edit-a-Program) settings.
## Troubleshooting date syncing
If the date fields are not used or updated as expected, check:
1. Can you edit the fields on that issue in Jira?
1. The fields need to be on the *(Issue) Screen* for the "Edit issue" operation. This can be configured separately for each Jira project based on the *Issue type screen scheme* for that project.
2. Users need permission to update the field in Jira, e.g. "Edit issue" permission.
2. Are there multiple date fields with the same name on your Jira site?
1. Use the ID number displayed in the field dropdowns in Easy Agile Programs to confirm which field is used.
2. For [team-managed projects (Jira Cloud only)](https://support.atlassian.com/jira-software-cloud/docs/learn-the-basics-of-team-managed-projects/), you'll need to add [the *global* date fields to the project](https://confluence.atlassian.com/jirasoftwarecloud/customize-work-item-fields-in-team-managed-projects-951392551.html) so that it can use the same fields as other projects in your Program. Avoid using fields created in a team-managed project, since these can't be used on issues outside that project.
A blue "Configure Date Syncing" button will appear on the [Program board](https://help.easyagile.com/easy-agile-programs/program-board.md) and [Edit roadmap page](https://help.easyagile.com/easy-agile-programs/schedule-features-epics-into-your-increment.md) if Easy Agile Programs isn't able to sync dates for all issues on the Roadmap.
This will still show if *some but not all* issues are correctly syncing.
Click the button to see the name and ID number of the date fields that need synchronizing.
### Issues appearing in the Shared Team Features swimlane
Easy Agile Programs will automatically place issues with dates in the "Shared Team Features" swimlane when the app is unable to determine which team the issues belong to.
* If you use "Jira epics from my team boards", they'll be automatically added to the correct team swimlane.
* Otherwise, all date-sync'd issues will be added to the "Shared team features" swimlane.
To resolve, drag the issue to the correct swimlane on the .
---
language: "en"
---
# Delivery Insights
## Delivery Insights
Delivery Insights helps you understand if your program is on track by surfacing patterns across multiple teams. You get a consolidated view of cycle time, throughput, and work in progress with recommendations.
Delivery Insights is available on Jira Cloud only.
### Why use Delivery Insights?
Delivery Insights helps delivery leaders maintain delivery predictability and stakeholder confidence:
* **Understand cross-team patterns:** See which teams are struggling and whether issues are systemic or isolated
* **Communicate with confidence:** Use evidence to support your stakeholder updates
* **Spot issues early:** Identify coordination problems before they become blockers
* **Make informed decisions:** Get specific recommendations on what to investigate or monitor
*** ** * ** ***
### How to access Delivery Insights
1. Open **Easy Agile Programs** in your Jira site
2. Navigate to **Reports** from the top navigation
3. Select **Delivery Insights** from the tabs
You can filter the report by selecting a **Program** and **Increment** from the dropdowns at the top of the page. The report shows data for all teams in the selected program that you have permission to view in Jira.
*** ** * ** ***
### Key components of Delivery Insights
The report analyses three key metrics that help you understand program delivery health: cycle time, throughput, and work in progress.
For each metric, you'll see observations about what the data shows, the impact on your program's delivery confidence, and specific recommendations for what to investigate or monitor.
#### Celebration
When your program shows particularly strong delivery patterns, you'll see a celebration at the top of the report. This might recognise predictable delivery, improving trends, or consistently fast completion times.
Celebrations don't appear on every report - they surface when the data shows meaningful positive patterns worth acknowledging with your teams.
#### Cycle Time: How Long Does Work Take?
Cycle time measures how long work items take to complete from the moment they start to when they're done. The report shows two key numbers: **median cycle time** (the typical completion time) and **peak cycle time at the 85th percentile** (accounting for items that take longer than usual).
**What does 85th percentile mean?**
The 85th percentile means that 85% of items are completed within this time frame; they have a cycle time of this many days or less.
**How we define cycle time:**
We define cycle time as the whole time a work item has spent in an In Progress status category. This is inherently contextual to your teams' workflow configuration in Jira.
**What the insights tell you:**
The insights help you understand whether your program can deliver predictably. Stable cycle times with low variation suggest you can commit to timelines with confidence. High variation or increasing trends signal that delivery timelines are becoming less predictable, which affects stakeholder confidence and planning accuracy.
#### Throughput: How Much Work Gets Completed?
Throughput measures how much work your program completes. You'll see the **weekly average throughput** (how many items complete per week on average) and the total**completed work items** for the period.
**What the insights tell you:**
This metric helps you gauge whether the program has the capacity to deliver on commitments. Increasing throughput suggests the program is building momentum, while declining throughput may indicate teams are facing obstacles or that work is more complex than expected.
#### Work in Progress: How Much Work Is Active?
Work in progress (WIP) shows how many items are actively being worked on across your program. The report displays **average daily WIP** and **peak WIP**with insights about the age of work items across the program.
**What the insights tell you:**
High WIP often signals that teams are juggling too much concurrent work, which can slow delivery and reduce predictability. The percentage of aging work helps you spot items that might be stuck or blocked. Lower WIP with few aging items typically indicates healthier flow and more predictable delivery.
*** ** * ** ***
### How to use Delivery Insights
#### Refresh report
The report refreshes automatically **every 7 days** to ensure everyone in your program refers to the same data during sync meetings and stakeholder updates. If you need to see the latest data sooner, click **Refresh report** at the top right of the page.
 You'll only see insights when work has been completed in the selected increment. If you've created a new increment or selected a future increment, the report won't show data until teams start completing work.
#### Sharing insights
To share the report with stakeholders, click '**Copy delivery insights link'** and paste the link. Everyone with access to the program will see the same report when they follow the link.
 If a user only has access to selected teams or work items within a program, then their version of the report will differ from somebody with full access. A warning message will be shown when we detect that a user doesn't have full access.
#### Team breakdown
Each metric section includes a collapsible team breakdown that shows the individual numbers for each team.
Expand these sections to helps you spot which teams are performing differently from the program pattern and can help you to identify teams that may need your attention. It is up to you to decide whether that's a concern or simply reflects the nature of their work.
You'll only see teams you have permission to view in Jira.
*** ** * ** ***
### Taking action on recommendations
The recommendations in each section are conversation starters, not prescriptions. They highlight patterns worth investigating and suggest questions to explore with your teams.
You have the context about your program's current priorities, constraints, and circumstances - use these insights to guide more informed conversations about where to focus your attention.
*** ** * ** ***
### Best practices \& tips
* Use Delivery Insights in your weekly syncs or when preparing stakeholder updates. The insights provide evidence-based conversation starters.
* Compare team patterns to understand whether variations are concerning or simply reflect different types of work.
* When you spot concerning patterns, dig deeper with the affected teams. The report surfaces signals - your teams have the context to understand what's driving them.
* Incomplete or inconsistent Jira data can affect report accuracy. Encourage teams to keep their boards and workflows up to date.
*** ** * ** ***
### FAQs
* **Why don't I see any data in the Delivery Insights report?** The report only shows insights when work has been completed in the selected increment. New or future increments won't have data until teams start completing work.
* **Why does the report look different from my team mates?** All users see the same report data for a given program and increment. However, you'll only see teams (Jira boards) you have permission to view in Jira.
* **How often does the data refresh?** The report refreshes automatically every 7 days. You can manually refresh using the "Refresh report" button if you need the latest data sooner.
* **Can I see insights for individual teams?** The team breakdown sections show metrics for each team. For deeper team-level insights with charts and trend analysis, see [Team Insights](https://help.easyagile.com/easy-agile-teamrhythm/team-insights) in Easy Agile TeamRhythm.
*** ** * ** ***
### Data \& privacy
#### Our commitment
We are committed to your organisation's security and privacy, and we deeply value our unblemished SOC 2 audit history. With that in mind, we've taken a conservative approach to how we handle your data for this functionality.
#### How your data is protected
##### 1. No customer data leaves your Jira instance
All of your sensitive Jira data - work item titles, descriptions, comments, assignees, and any other personally identifiable information - remains securely within your Jira instance. This data never leaves your environment.
##### 2. We calculate metadata only
Instead of sending your actual Jira data, we calculate data about the data as the basis for our statistics. This metadata consists of aggregate numbers, percentages, and statistical measures that describe patterns in your workflow.
##### 3. Limited identifiers transmitted
No personally identifiable information is transmitted. Identifiers are limited to only Agile Board and Jira Work Item IDs to enable:
* Accurate insights
* Click through to work items
##### 4. Client-side enrichment
When the AI analysis returns, we enrich the response with Jira Work Item Keys (e.g. "USM-7780") on the client side---meaning in your browser, not on our servers. This ensures that readable work item references never leave your control.
If you have questions about how your data is handled or concerns about privacy:
* Review our full privacy policy at
* Contact our support team via the Help \& Support section
* Consult with your organisation's security team
*** ** * ** ***
### Share your feedback
We're continuously improving Delivery Insights based on your feedback.
Planned enhancements include feature level insights, visual charts, and advanced filtering. [Share your feedback](https://arijea.atlassian.net/servicedesk/customer/portal/20/create/992?customfield_11100=E-43M-MAJ-V3D-QHA&customfield_12995=1370c6e2b57a47f526f2a501dc74be9f)
---
language: "en"
---
# Dependencies: visualizing links between items
When planning work across teams, it's important to manage the dependencies between different pieces of work. This allows you to see and remove blockers so that your teams can execute smoothly.
[For a visual introduction to dependencies in Easy Agile Programs, check out this walkthrough](https://easyagile.storylane.io/share/jhlytyl3oqww).
## Visualizing dependencies
In Easy Agile Programs, you can visualize links between Jira issues as dependency lines.
This means that an issue link like "is blocked by" will show as a line between the two issues in Easy Agile Programs.
### How many dependency/link types will show?
Each Program is configured with 1 *issue link type* from Jira as the "default" dependency link type (see [Configuring dependencies for a Program](https://help.easyagile.com/easy-agile-programs/configuring-dependencies-for-a-program.md) for details). This will be toggled on automatically for all users.
We've recently added the option to view additional issue link types as dependencies.
Open the "Dependencies" dropdown on any page to select link types from Jira. This will be saved only for you.
Additional dependency link types are available:
* On Jira Cloud (i.e. Jira sites with "....atlassian.net" in the URL) on all pages of the app
* In Data Center version 7.3.0+
In older versions of the app, the "Type" section will be missing from the "Dependencies" dropdown. Only the 1 dependency link type configured for the Program will be shown.
### On the Program board
Use the Program board page to see an overview of the dependencies across your Increment or Release Train.
Try the new [Dependency map](https://help.easyagile.com/easy-agile-programs/dependency-map.md) to focus on only the issues with dependencies!
### On the Team planning page
On the [**Team planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md), you can track both in-team dependencies and dependencies with other teams.
Add another team from your Program using the "Other teams" button in the top right. If there are already dependencies with that team, you'll see colored numbers describing the health of those dependencies.
Use this to visualize how your team's work depends on or enables other teams.
By seeing the potential blockers and sequencing work as needed, you can enable smoother cross-team work towards your shared goals.
### Dependency details
When you hover over a dependency line, you'll see an  information icon. Click this to see the details of this dependency link.
On earlier versions of Easy Agile Programs, there is a  cross icon when you hover on a dependency line (instead of an information icon). This will trigger a pop-up asking you if you want to delete this issue link from the Jira issues.
## Understanding dependency status
Learn more about [Understanding dependency status, health, and color](https://help.easyagile.com/easy-agile-programs/understanding-dependency-status-health-and-color.md).
### Color-coded dependency lines
Dependency lines show in different colors depending on the health of the dependency. This quickly identifies if the work is scheduled in the correct order.
* **Red: Conflict**
* **Orange: At risk**
* **Green: Healthy**
**External** dependencies are links with work that's *not* in this Program/Increment.
The health of these dependencies can't be calculated, so is shown in **black**.
[Learn more about dependency health and external dependencies](https://help.easyagile.com/easy-agile-programs/understanding-dependency-status-health-and-color.md).
### Done dependencies
Easy Agile Programs filters out done dependencies so you can focus on the dependencies that need your attention.
Easy Agile Programs checks the *Status Category* of the two linked issues to calculate if a dependency is "Done". If one or both of the issues are already in *any* "Done" Status, the dependency is counted as Done.
[Learn more about Done dependencies](https://help.easyagile.com/easy-agile-programs/understanding-dependency-status-health-and-color.md#Understandingdependencystatushealthandcolor-Donedependencies).
## Filtering dependencies
### Dependency map
Try the new [Dependency map](https://help.easyagile.com/easy-agile-programs/dependency-map.md) to focus on only the issues with dependencies!
### Show/hide dependency lines based on health
You can switch dependency lines on and off based on their health/color. For example, you might switch off green Healthy dependencies so that you can focus on resolving At-risk and Conflict plans.
Find these options in the "Dependencies" dropdown in the header on any page.
*In older versions of Easy Agile Programs on Data Center (v7.2.0 and earlier), dependency options are in the "View settings" dropdown only on the Program board page.*
### Filtering issues by dependencies, Status or Team board
Open the Filters panel on the Program board to filter the page based on Dependency health, Status category, or Team/board.
For example, you might choose to show issues with At risk or Conflict dependencies so that you can assess these potential risks.
Note: If two issues visible with these filters *also* have a dependency of a *different* color, that other link will show too.
## Creating and editing dependencies
There are two ways to create dependencies between issues:
1. Create a dependency between two team-level issues on the [**Team planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md).
2. Add an issue link to an issue in Jira.
It's currently only possible to create dependencies *between two team-level issues* within the app.
### Creating dependencies between team-level issues in Easy Agile Programs
On the [**Team planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md), switch to "Create dependencies" mode using the button in the header. The button will be dark when this mode is enabled.
In "Create dependencies" mode, click two issues to create a new dependency:
1. The issue that requires something
2. The issue that unblocks the first issue
In newer versions of the app, you'll see help text on the line that says what link type and direction you'll create.
This issue link will be added to the issues in Jira.
Add another team to view and manage dependencies across teams.
Use the "Other teams" button in the header to add another team to the page.
You can use "Create dependencies" mode to create cross-team dependencies as well.
### Creating dependencies in Jira
Add an issue link in Jira to see that link on the issue in Easy Agile Programs. To do this, edit the issue in Jira.
| **Jira Cloud** (has "....atlassian.net" in the URL) | **Jira Data Center** |
|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| In the "+ Add" dropdown, use the 🔗 "Link issue" option:  | Under the "More" menu, use the "Link" option.  |
| [See Atlassian's guide for Jira Cloud.](https://support.atlassian.com/jira-software-cloud/docs/link-issues/) | [See Atlassian's guide for Jira Data Center.](https://confluence.atlassian.com/jiracoreserver/linking-issues-939937913.html) |
The issue link type will need to match the *Dependency link type* configured for the Program.
* View the details of any existing dependency to check the issue link type it uses.
* A user with [**Manage Programs** permission](https://help.easyagile.com/easy-agile-programs/permissions.md#The%25E2%2580%259CManagePrograms%25E2%2580%259Dpermission) can see the *Dependency link type* in the [Edit Program](https://help.easyagile.com/easy-agile-programs/create-a-program.md#CreateandeditaProgram-EditaProgram) menu.
If you have the latest version of the app, you'll also see the issue link type named in the Dependencies map panel on the Program board page.
### Deleting dependencies
When viewing the Dependency details modal, you'll have the option to delete a dependency link. This will delete the issue link in Jira.
If you've made a mistake, watch for a flag in the bottom left of your screen with an "Undo" button.
You can also remove the issue link from the issue in Jira. The dependency line will be gone the next time you load or refresh the Easy Agile Programs app.
On earlier versions of Easy Agile Programs, there is a  cross icon when you hover on a dependency line (instead of an information icon). This will trigger a pop-up asking you if you want to delete this issue link from the Jira issues.
## Troubleshooting dependencies
If dependency lines aren't working as expected, [reach out to the Easy Agile support team](https://arijea.atlassian.net/servicedesk/customer/portal/2/group/97/create/233?customfield_12467=11013&summary=Re%3A+Troubleshooting+dependencies)!
### What permissions are required to create or edit dependencies?
To create new issue links, you'll need the "Link Issues" permission. If the issues you want to link are from different Jira projects, you'll need this permission for both projects.
If you don't have permission to create issue links in Jira, you'll see an error when trying to create dependencies in Easy Agile Programs.
A Jira Administrator can update these permissions by editing the Permissions Scheme for the project(s). See Atlassian's guide [for Jira Cloud](https://support.atlassian.com/jira-cloud-administration/docs/manage-project-permissions/) or [for Jira Data Center](https://confluence.atlassian.com/adminjiraserver/managing-project-permissions-938847145.html).
### Some dependency lines are missing, even though they're the correct issue link type
The "Linked issues" field might be hidden on the [Issue Screen](https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-screens/). This doesn't stop the "Linked issues" section showing in the Jira issue view, but does prevent apps like Easy Agile Programs from loading issue link data.
### Changing the dependency configuration
Users with [**Manage Programs** permission](https://help.easyagile.com/easy-agile-programs/permissions.md#The%25E2%2580%259CManagePrograms%25E2%2580%259Dpermission) can change the dependency link type for a Program. [Learn more about configuring dependencies](https://help.easyagile.com/easy-agile-programs/configuring-dependencies-for-a-program.md).
*** ** * ** ***
## Other ways of visualising dependencies and blockers
[Visualize Flags (impediments) from Jira](https://help.easyagile.com/easy-agile-programs/customising-issue-cards.md#VisualizingFlags/impedimentsfromJira) in Easy Agile Programs.
[See scheduling conflicts when the issues for an Epic are scheduled outside the dates for that Epic](https://help.easyagile.com/easy-agile-programs/program-board.md#ManagingSchedulingConflicts).
---
language: "en"
---
# Dependencies report
**The Dependencies report is available:**
* on Jira Cloud (i.e. Jira sites with "....atlassian.net" in the URL)
* on Jira Data Center with app version 7.0.0+, with more filtering options added in v7.1.0
The Dependencies report provides summarized information about the dependencies in an Increment. This helps you identify which dependencies could be a risk so that you can anticipate problems before they happen.
## Configuring the dependencies report
⚙️
The report will show dependencies based on the "Dependency link type" [configured for this Program](https://help.easyagile.com/easy-agile-programs/configuring-dependencies-for-a-program.md). By default, this is "blocks" / "is blocked by". Changing the "Dependency link type" in the "Edit Program" menu will change the link type for all Increments, teams, and users in this Program.
When you open the Report tab from an existing Increment, the report will be displayed for this Increment.
Adjust these settings to choose the focus of this Report:
* Choose a different Program, or a different Increment within that Program
* Add or remove teams to filter or focus the report
* In the "More options" dropdown, choose to show or hide:
* Dependencies where both issues are in this Increment and in the same team (i.e. scheduled on the same [**Team planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md))
* Dependencies where one or both linked issues are already [done](https://help.easyagile.com/easy-agile-programs/dependencies.md#Done-dependencies)
These settings will impact the calculations for all sections on the Reports page.
Your configuration selection will be reflected in the page URL. This means that you can share a link with a teammate and they'll see the report for the *same* Increment and Teams!
## Dependencies health summary
See a summary of the health of dependencies in this Increment. This is a count of the [dependency lines you'll see on the Program Board](https://help.easyagile.com/easy-agile-programs/dependencies.md).
Easy Agile Programs calculates the health of a dependency based on the sprints the issues are scheduled in:
* A **red Conflict** is when the issues are scheduled in the wrong order: the issue that needs to be done *first* is scheduled *later*. Rescheduling these issues removes blockers from your teams!
* An **orange At risk** dependency is when both issues are scheduled in the *same* sprint. Teams will need to work carefully during that sprint to complete this work.
* A **green Healthy** dependency is when the issues are scheduled in the right order. You don't need to take action for this sequence to work.
* An **External** dependency is a link to an issue that isn't scheduled in this Increment. Easy Agile Programs can't calculate the health of this dependency; check the details of the issues involved.
Identifying and reducing the number of Conflicts and At risk dependencies helps unblock work.
## Teams dependencies matrix
Surface the dependencies for specific to see which teams could be blocked, or which could be blocking others.
The Teams dependencies matrix shows a sum of the dependencies connected to each team in this Increment. The sum is split by the *direction*of the dependency link (e.g. "blocks" links are counted separately from "is blocked by").
* Toggle "Show healthy dependencies" to change whether to count dependency links that are already scheduled in the correct order.
Click on a number to view the list of dependency links for that team and link direction. This will show a summary of the linked issues and when each is currently scheduled.
For example, to see what's blocking the Marketing Creatives team, select the number in the "is blocked by" column for that team:
## Export the dependencies report
Exporting reports is available:
* on Jira Cloud (i.e. Jira sites with "....atlassian.net" in the URL)
* on Jira Data Center with app version 8.4.2+; [a Jira Administrator can install the latest version](https://confluence.atlassian.com/upm/updating-apps-273875710.html).
Use the the "export"/"download" button to generate a downloadable PNG of the report, using the currently-selected Program, Increment and Teams.
This can be added to other documents or reports for stakeholders who can't access the live report personally.
## More dependency visualization
We're building more reports. [Tell us what you need](https://forms.gle/BtQ8wdfU5zDmEPxHA)!
To focus on dependency links in-situ in your Increment, try the [Dependency map](https://help.easyagile.com/easy-agile-programs/dependency-map.md).
For more information about dependency lines in Easy Agile Programs, see [Dependencies: visualizing issue links](https://help.easyagile.com/easy-agile-programs/dependencies.md).
---
language: "en"
---
# Dependencies map
**The Dependencies map is available:**
* on Jira Cloud (i.e. Jira sites with "....atlassian.net" in the URL)
* on Jira Data Center with app version 6.4.0+; [a Jira Administrator can install the latest version](https://confluence.atlassian.com/upm/updating-apps-273875710.html).
Use the Dependencies map on the Program board to focus on *only* the planned work that's interdependent.
Instead of showing or hiding the dependency *lines*, this allows you to filter issue cards based on whether they have dependencies.
We recommend using this view to identify the dependencies that could become blockers or bottlenecks in your Program. The dependencies that could pose a risk to the planned work include:
* At risk or Conflict dependencies
* An issue that blocks many other issues in a bottleneck
* A chain of issues that must be done in sequence
Note:
* Other Filters (e.g. Status, Team) will *not* be applied to this view.
* Team-level issues will *always* show, even if you've switched them off in the "View settings" dropdown.
## Filtering the dependency map
### Select dependency link types
Dependency link type selection is available:
* On Cloud
* On Data Center v7.3.0+
Select additional issue link types from Jira to display as dependency lines.
The [dependency link type configured for this Program](https://help.easyagile.com/easy-agile-programs/create-a-program.md#6.-Choose-a-dependency-link-type) will be selected by default.
### Highlight critical dependencies
Critical dependencies filter available:
* On Cloud
* On Data Center v8.2.0+
Critical dependencies are the ones that represent the highest risk: if these dependencies aren't done, it will disrupt the flow of work.
Note: other filters are disabled when using a critical dependency filter.
#### Bottlenecks
A **bottleneck** is when:
* multiple issues depend on one issue, or
* one issue depends on multiple other issues.
Use the Bottlenecks toggle to filter down to only issues with bottleneck dependencies.
#### Chains
A **chain** is when 3 or more issues are linked in a series. These issues can only be done in a specific sequence.
Use the Chains toggle to show only issues in dependency chains.
### Filter by dependency health
Use the checkboxes to filter issues based on the health of their connected dependencies.
### More filtering options
"More options" is available:
* On Jira Cloud (i.e. Jira sites with "....atlassian.net" in the URL)
* In Data Center v7.1.0+
**Same-team dependencies:** Filter out dependencies where both issues are managed by the same team to more easily manage cross-team dependencies.
**Done dependencies:** To focus on the dependencies that need attention, filter out [done dependencies](https://help.easyagile.com/easy-agile-programs/dependencies.md#Done-dependencies). Done dependencies in the Dependency map view are toggled off by default on Cloud.
## More dependency insights
See a configurable overview of dependencies in the Increment in the [Dependencies report](https://help.easyagile.com/easy-agile-programs/dependencies-reports.md).
---
language: "en"
---
# Easy Agile Programs API
Easy Agile Programs provides an API for integration with other systems.
We currently do not support API access for the Cloud version of Easy Agile Programs.
The documentation below is valid as at Easy Agile Programs 6.4.0 on Jira Server and Data Center.
Notes:
* agileBoardSprints is a mapping between sprintIds and columns for each Scrum board in an increment
* Issues in Scrum boards are scheduled by assigning them to sprints in Jira Software
* Issues in Kanban boards are scheduled using an issue entity property (as Kanban agile boards do not support sprints)
* startDate is a Unix timestamp in UTC at the start of the calendar day of the increment
* endDate is a Unix timestamp in UTC at the end of the calendar day of the increment
* Start and end dates of individual sprints are calculated from the increment startDate and the sprintCadences properties(sprintPosition, weekCount)
* issueLink... are used to set a link type other than Epic Link
*** ** * ** ***
## Get Program
**GET** */rest/eap/latest/program/{programId}*
Sample Response:
|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| { "id": 199, "config": { "programFieldId": "customfield_10202", "programIncrementFieldId": "customfield_10201" }, "name": "Test jcma program 2(same id)", "objectives": "", "dependencyLinkDirection": "inward", "dependencyLinkTypeId": "10000", "issueLinkMethod": "epic", "startDateFieldId": "customfield_10200", "endDateFieldId": "duedate", "boardIds": [ 54 ], "increments": [ { "id": 301, "name": "INC123", "objectives": "", "number": 0, "agileBoardSprints": [], "startDate": 1709251200000, "endDate": 1715302800000, "usingGlobalSprints": false, "isDateSyncingEnabled": true, "sprintCadences": [ { "sprintPosition": 0, "weekCount": 2 }, { "sprintPosition": 1, "weekCount": 2 }, { "sprintPosition": 2, "weekCount": 2 }, { "sprintPosition": 3, "weekCount": 2 }, { "sprintPosition": 4, "weekCount": 2 } ] } ], "boardSettings": [ { "boardId": 54, "extraIssueCardFields": [] } ], "l3IssueLinkTypes": [] } |
*** ** * ** ***
## Get Program Increment
**GET** */rest/eap/latest/program/increment/{incrementId}*
Sample response:
|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| { "id": 366, "name": "test", "objectives": "", "number": 0, "agileBoardSprints": [], "startDate": 1712620800000, "endDate": 1718668800000, "usingGlobalSprints": false, "isDateSyncingEnabled": true, "program": { "id": 2, "config": { "programFieldId": "customfield_10202", "programIncrementFieldId": "customfield_10201" }, "name": "Commercial Space Travel", "objectives": "{\"version\":1,\"type\":\"doc\",\"content\":[{\"type\":\"heading\",\"attrs\":{\"level\":3},\"content\":[{\"type\":\"text\",\"text\":\"Program Objectives:\"}]},{\"type\":\"paragraph\",\"content\":[{\"type\":\"text\",\"text\":\"- Provide a safe, quality and first-to-market commercial space travel experience\"},{\"type\":\"hardBreak\"},{\"type\":\"text\",\"text\":\"- Deliver a fun and fully integrated passenger experience \"},{\"type\":\"hardBreak\"},{\"type\":\"hardBreak\"},{\"type\":\"text\",\"text\":\"Release Train Engineer:\",\"marks\":[{\"type\":\"strong\"}]},{\"type\":\"text\",\"text\":\" Alice Zhu\"},{\"type\":\"hardBreak\"},{\"type\":\"text\",\"text\":\"Product Manager:\",\"marks\":[{\"type\":\"strong\"}]},{\"type\":\"text\",\"text\":\" James Hayes\"}]}]}", "dependencyLinkDirection": "inward", "dependencyLinkTypeId": "10000", "issueLinkMethod": "epic", "l3BoardId": 374, "startDateFieldId": "customfield_10401", "endDateFieldId": "customfield_10402", "boardIds": [ 12, 6, 7, 8, 13, 2 ], "increments": [], "boardSettings": [ { "boardId": 12, "extraIssueCardFields": [] }, { "boardId": 6, "extraIssueCardFields": [] }, { "boardId": 7, "extraIssueCardFields": [] }, { "boardId": 8, "extraIssueCardFields": [] }, { "boardId": 13, "extraIssueCardFields": [] }, { "boardId": 2, "extraIssueCardFields": [] } ], "l3IssueLinkTypes": [ { "issueLinkMethod": "parent" }, { "issueLinkMethod": "issue-link", "issueLinkDirection": "outward", "issueLinkTypeId": "10300" } ] }, "sprintCadences": [ { "sprintPosition": 0, "weekCount": 2 }, { "sprintPosition": 1, "weekCount": 2 }, { "sprintPosition": 2, "weekCount": 2 }, { "sprintPosition": 3, "weekCount": 2 }, { "sprintPosition": 4, "weekCount": 2 } ] } |
*** ** * ** ***
## Get Milestones
Milestones are independent of the issues and are only used as markers within programs, therefore you cannot query for all issues within a milestone.
GET /rest/eap/latest/program/{programId}/milestones
Sample response:
|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| [ { color: "#008DA6", endDate: null, id: 14, name: "System Demo", programId: 27, startDate: "2020-06-30T00:00:00.000Z", type: "DATE_MARKER" }, { color: "#6554C0", endDate: null, id: 13, name: "Inspect & Adapt", programId: 27, startDate: "2020-08-24T00:00:00.000Z", type: "DATE_MARKER" } ] |
*** ** * ** ***
## Get Team PI Objectives
**Availability**: Easy Agile Programs version 4.6.0 and later
**GET** /rest/eap/latest/program/{incrementId}/{boardId}/teamObjectives
Successful response type: an *array* of JSON objects:
JSON
{
actualValue?: number | null;
boardId: number;
description?: string;
id: number;
incrementId: number;
name: string;
planValue?: number | null;
type: "Committed" | "Uncommitted";
}[]
Sample response:
JSON
[
{
"id": 38,
"name": "Objective two",
"planValue": 3,
"type": "Uncommitted",
"incrementId": 513,
"boardId": 1136
},
{
"id": 37,
"name": "Objective one",
"planValue": 5,
"type": "Committed",
"description": "Objective description",
"incrementId": 513,
"boardId": 1136
}
]
*** ** * ** ***
## **Get Issue Entity Properties with JQL and the API**
Issues on Kanban boards and issues on the Roadmap are scheduled with issue entity properties. You can search for these using JQL:
* Search for roadmap issues in a specific increment with the following JQL query:
* `issue.property[EAP-schedules].tags ~ i_{incrementId}_tr`
* Search for Kanban issues in a specific increment with the following JQL query:
* `issue.property[EAP-schedules].tags ~ i_{incrementId}_ti`
Then fetch the entity property using the Jira Core REST API: /rest/api/2/issue/{issueKey}/properties/EAP-schedules
**Sample issue entity property for Roadmap schedule**
|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| JSON { key: "EAP-schedules", value: { schedules: [ { endColumn: 4, incrementId: 79, programId: 34, startColumn: 1, type: "ROADMAP" } ], tags: "p_34 i_79 i_79_tr" } } |
**Sample Kanban schedule**
|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| JSON { key: "EAP-schedules", value: { schedules: [ { boardId: 89, columnIndexes: [ 4 ], incrementId: 79, programId: 34, type: "ISSUE" } ], tags: "p_34 i_79 i_79_ti" } } |
---
language: "en"
---
# eazyBI
## **Creating reports in eazyBI using the Program and Program Increment Custom Fields**
The Program and Program Increment custom fields are not currently natively detected by eazyBI.
In order for eazyBI to detect the Program and Program Increment custom fields for each of your Programs or Program Increments, we need to map their IDs by following these steps:
* Identifying the Program and Program Increment Custom Field IDs created by Easy Agile Programs
* Giving eazyBI the Program and Program Increment Custom Field IDs
*** ** * ** ***
### Identifying the Program and Program Increment Custom Field IDs
1. Navigate to the **Administration** cog and click **Issues**
2. Select **Custom Fields** from the menu on the left hand side. Locate the **Program** and **Program Increment** custom fields from the list
a) Click the cog and hover over the the **Configure** option in the dropdown
b) Observe the URL at the bottom left of the browser window. For example, the Program Increment custom field ID below is **10201.**
*** ** * ** ***
### Giving eazyBI the Program and Program Increment Custom Field IDs
1. Navigate to the Settings Cog in the eazyBI Global Navigation Bar and select **Settings**
2. Select **Advanced Settings** and copy and paste the following snippet - replace the custom field IDs in the example below with your own as discovered in the above steps and click **Update advanced settings**
|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| #Program from Easy Agile Programs [jira.customfield_10304] data_type = "string" dimension = true multiple_values = true split_by = "," #Program Increment from Easy Agile Programs [jira.customfield_10303] data_type = "string" dimension = true multiple_values = true split_by = "," |
3. Navigate to **Source Data** in the eazyBI Global Navigation bar and under the **Actions** heading select **Edit** \> this will take you to the **Jira import options** screen
4. Select the **Custom fields** tab. You should now see the Program and Program Increment custom fields in the list. Select **Import as dimension** and **import as property** for both and click **Import**
---
language: "en"
---
# Estimation and capacity
Easy Agile Programs allows for capacity management on the [**Team planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md) for Scrum boards using **Story points**.
## Sprint capacity
The team's capacity can be manually entered for each sprint, allowing for capacity changes due to holidays and other commitments.
Estimates can be added directly to each issue from the Team Planning Board. Simply click on the grey field in the bottom left hand corner to add the team's estimate. The story points are added up and shown at the top of the sprint so you can easily see if you are over- or under-committed.
To edit the capacity of a sprint, you'll need either **Manage Sprints** or **Edit Sprints** permission for *all* projects that have issues in that sprint.
## Troubleshooting estimation and capacity
### Failed to update capacity due to permissions
**Error message**:
> **Failed to update capacity of \[sprint name\]**
>
To update this sprint, you must either have the Manage Sprints or the Edit Sprints permission for all of the following projects: \[project list\].
**Resolution:** A Jira Administrator can grant "Manage Sprints" or "Edit Sprints" permission by editing the project's Permission Scheme in [Jira Cloud](https://support.atlassian.com/jira-cloud-administration/docs/permissions-for-company-managed-projects/) or [Jira Data Center](https://confluence.atlassian.com/adminjiraserver/managing-project-permissions-938847145.html).
* You'll need this permission for each project that has issues in the sprint.
* There might be issues in the sprint that *aren't* on this team board or visible in Easy Agile Programs. Running a [JQL search in Jira](https://www.atlassian.com/blog/jira/jql-the-most-flexible-way-to-search-jira-14) for the sprint can help you find *all* the Jira issues in that sprint.
### Why can't I see/set sprint capacity on my Team Planning Board?
To see sprint capacity on the Team Planning Board, the Board setup needs to:
* be a Scrum board (not Kanban or a team-managed project)
* use Estimates in Story Points (not time estimates)
### Why don't you allow estimations for Kanban boards?
One of the challenges we have with estimation is that Jira itself doesn't support estimation on Kanban boards. Technically you can add an estimation field to the screen and enter values but Jira won't understand it as an estimation.
Kanban boards are missing the settings screen to configure estimation, any reports around estimation and most critically for us, the APIs to set / update the estimation.
We typically try to follow Atlassian's lead on features like this as it would be challenging to maintain our own implementation of estimation configuration.
*Do you estimate sprints in other units? Do you use estimates on Kanban boards? Let us know* [*here*](https://arijea.atlassian.net/servicedesk/customer/portal/2/group/2/create/30)*.*
---
language: "en"
---
# FAQs
Most of our FAQs can be found on the relevant pages of the [Purchasing \& Admin](https://help.easyagile.com/easy-agile-programs/purchasing-administration.md) or [How-To section](https://help.easyagile.com/easy-agile-programs/how-to-guides.md). If you can't find the answer you're looking for, please [reach out to our Customer Support Team](https://arijea.atlassian.net/servicedesk/customer/portal/2/group/2/create/30) and we'll be happy to help.
## Can I define the fields shown in the in-app issue view when I click on an issue-key in Easy Agile Programs? \[Data Center only\]
The issue view in Easy Agile Programs for Jira Data Center currently shows the following fields:
* Summary
* Description
* Components
* Assignee
* Versions
* Status
* Sprint
The following field types are also supported, provided they are on the 'Edit Issue' screen being used by your Project:
* Single \& multi-line text fields
* Single \& multi-select list fields
* Numeric fields
In order to see these fields in the in-app issue view, a Jira Administrator will need to add any relevant fields to the screen being used by your Project.
[Here is a link to an Atlassian doc](https://confluence.atlassian.com/adminjiracloud/add-a-custom-field-to-a-screen-991923749.html#:~:text=Select%20%3E%20Issues.,Associate%20this%20field%20to%20screens) which walks you through how to add a field to a screen.
We'd love to hear what other field types you would like supported in the issue view [here](https://arijea.atlassian.net/servicedesk/customer/portal/2/group/2/create/30).
## Why does my Program only show the top header of the app?
If the Program only shows the top header of the app, the issue might be caused by an invalid announcement banner.
If your instance has an announcement banner configured please verify that the code snippet used is valid HTML and that all tags are closed. You can find documentation on configuring your announcement banner [here](https://confluence.atlassian.com/adminjiraserver/configuring-an-announcement-banner-938846985.html).
## Why am I seeing "User-installed apps may not be compatible"?
When enabling a Content Delivery Network (CDN) on Jira Data Center you will be presented with this warning message about Easy Agile Programs. Despite the warning, the app will continue to function unless you have users that use Internet Explorer 11 (IE11) to access the app.
If you would like to enable the CDN and have IE11 users, please reach out to our Support Team [here](https://arijea.atlassian.net/servicedesk/customer/portal/2/group/2/create/30).
## No Projects available error (Data Center / Server only)
There is an issue in Jira Data Center / Server that prevents Easy Agile apps from obtaining the list of projects referenced by your board filter. We need the list of projects to provide functionality on the story map such as quick issue create and version swimlanes.
This error appears when an agile board filter excludes a project or has a complex query where Jira can not determine the projects included.
For example, the following filter query will not allow us to retrieve a list of projects that *are* included in the filter:
SQL
project != KANBAN order by rank
Even more interesting is that if you explicitly specify a project and then exclude another, Jira Software still doesn't return the list of projects:
SQL
project = SCRUM and project != KANBAN order by rank
If you run into this issue, you will need to list the projects to include explicitly. i.e.
SQL
project in (SCRUM, FOO, BAR) order by rank
There is a bug on the Atlassian Jira Software backlog which tracks this issue: [JSWSERVER-16172](https://jira.atlassian.com/browse/JSWSERVER-16172). We encourage you to vote and comment on that issue to show your support for its resolution.
If this does not solve your issue, [please reach out to the Easy Agile Support Team](https://arijea.atlassian.net/servicedesk/customer/portal/2) and we will be happy to help!
---
language: "en"
---
# Filtering Delivery Insights
## Why Use Filtering?
Delivery Insights allows you to customise the analysis to focus on specific time periods and work item types. This helps you gain deeper insights into particular aspects of your teams delivery.
## Accessing Filters
To access the filtering options:
1. Navigate to the **Reports** tab
2. Click on the **Delivery Insights** sub tab.
3. Click the **Filters** button in the top right corner of the page
4. The filter panel will open on the right side
The filters button displays the number of active filters (e.g. "Filters / 4" means four filters are currently applied).
*** ** * ** ***
## Excluding non-working days from the Delivery insights
The **Non-working Days** filter lets you customise your Delivery Insights report to include or exclude weekends based on your operational needs.
### How to exclude non-working days from Delivery insights report
1. In the **Filters** panel, locate the **Non-working Days** section
2. Select any non-working days that you want to exclude from the calculations (i.e Friday; Saturday; Sunday) by clicking on them. Multiple choices is available.
3. Click **Apply**to refresh the report.
*** ** * ** ***
## Work Item Types
The Work Item Types filter allows you to focus the analysis on specific types of level 0 work items, such as Tasks, Bugs, Stories, Feature Requests, Experiments, or Support tickets.
### How to Filter by Work Item Type
1. In the **Filters** panel, locate the **Work Item Types** section
2. By default, all level zero work item types (Task, Bug, Story,etc) relevant to the boards in the program are selected.
3. Click the **X** next to any work item type to remove it from the filter.
4. Click the **dropdown arrow** or clear button to see all available work item types.
5. Select additional work item types by clicking on them.
### Available Work Item Types
The available work item types depend on your Jira configuration. Common options include:
* **Task** (✓ checkbox icon)
* **Bug** (🐞 bug icon)
* **Story** (📑 bookmark icon)
### Why Filter by Work Item Type
Filtering by work item type allows you to:
* **Compare performance across types:** See if bugs are taking longer than stories
* **Focus on specific work:** Analyse only feature development or only bug fixes
* **Identify patterns:** Understand if certain types of work have consistent bottlenecks
* **Tailor retrospectives:** Focus discussions on specific types of work
**Example scenarios:**
* Filter to only **Bugs** to analyse your team's defect resolution process
* Filter to **Stories** to understand feature delivery cycle time
* Combine **Task** and **Story** to exclude bugs from your main flow analysis
* Select only **Feature Request** to review how customer-requested features are progressing.
*** ** * ** ***
## Applying Filters
Once you've selected your desired filters:
1. Review your selections in the filter panel
2. Click the **Apply** button at the bottom of the filter panel
3. Delivery Insights will refresh with the new filter criteria
The page will reload and regenerate insights based on your filtered selection. This may take a few moments as the analysis is recalculated.
*** ** * ** ***
## Understanding Filtered Results
When filters are applied:
* The **filter count** is displayed on the Filters button (e.g. "Filters / 3")
* All **charts** update to show only the filtered data
* All **insights and recommendations** are recalculated based on the filtered dataset
* **Work item keys** mentioned in insights will only include items matching your filter criteria
### Impact on Charts
Each chart responds to your filter selections:
* **Cycle time**: Shows only work items of the selected types completed in the selected increment period.
* **Throughput:** Displays completion rates for only the filtered work item types.
* **Work in progress (WIP):**Shows work in progress for only the selected types.
*** ** * ** ***
## Filter limitations
* Filters apply to the entire Delivery Insights view and cannot be set differently for individual sections
* Filtering to very small datasets (e.g. only 2-3 completed items) may result in limited or less meaningful insights
* Custom fields and labels are not currently supported as filter options
---
language: "en"
---
# Get Started: Set up Easy Agile Programs
Learn how to set up and configure Easy Agile Programs for your organisation.
Here you'll find key steps for Jira Administrators or users with [**Manage Programs** permission](https://help.easyagile.com/easy-agile-programs/permissions.md#The%25E2%2580%259CManagePrograms%25E2%2580%259Dpermission) to get Easy Agile Programs up and running for your organisation.
[See this guide on finding the Easy Agile Programs app in your Jira site](https://help.easyagile.com/easy-agile-programs/navigate-to-your-program.md).
* [Configuring Jira for Easy Agile Programs](https://help.easyagile.com/easy-agile-programs/configuring-jira-for-easy-agile-programs.md)
* [What is a "team" in Easy Agile Programs? Configuring Jira boards](https://help.easyagile.com/easy-agile-programs/what-is-a-team-in-easy-agile-programs-configuring-.md)
* [Create and edit a Program](https://help.easyagile.com/easy-agile-programs/create-a-program.md)
* [Create and edit a Program Increment](https://help.easyagile.com/easy-agile-programs/create-and-edit-a-program-increment.md)
* [Programs custom fields](https://help.easyagile.com/easy-agile-programs/programs-custom-fields.md)
* [Integrations](https://help.easyagile.com/easy-agile-programs/integrations.md)
---
language: "en"
---
# Help & Support
Couldn't find an answer to your question? The Easy Agile team are here to help!
Quick troubleshooting tips: [Troubleshooting Easy Agile apps](https://help.easyagile.com/easy-agile-support/troubleshooting-easy-agile-apps.md)
* [FAQs](https://help.easyagile.com/easy-agile-programs/faqs.md)
* [How to raise a support request](https://help.easyagile.com/easy-agile-programs/how-to-raise-a-support-request.md)
* [How to Raise a Feature Suggestion](https://help.easyagile.com/easy-agile-programs/how-to-raise-a-feature-suggestion.md)
---
language: "en"
---
# How-To Guides
Learn how to use Easy Agile Programs to plan, align, and track work across teams.
[Easy Agile Programs for Jira](https://marketplace.atlassian.com/apps/1219491/easy-agile-programs-for-jira?hosting=server&tab=overview) empowers Release Train Engineers and Program Managers to align remote, distributed or face-to-face teams with a holistic view of your Program right inside Jira.
Teams are able to schedule work committed within the PI and create dependencies without leaving the Program.
Visualise and manage team dependencies, create milestones, and set PI objectives for effective PI Planning.
Here you'll find documentation on how to get started as well as how to visualise and manage team dependencies, set PI objectives and create milestones for effective PI Planing.
## Watch a demo
For a full run through of how to use Easy Agile Programs, please watch our [on-demand demo](https://www.easyagile.com/products/programs/product-demo/?utm_source=easy-agile-programs&utm_medium=docs&utm_campaign=how-to).
* [Programs app Demo](https://help.easyagile.com/easy-agile-programs/product-demo.md)
* [Navigating Easy Agile Programs](https://help.easyagile.com/easy-agile-programs/the-anatomy-of-easy-agile-programs.md)
* [Planning on the Increment roadmap](https://help.easyagile.com/easy-agile-programs/schedule-features-epics-into-your-increment.md)
* [Dependencies: visualizing links between items](https://help.easyagile.com/easy-agile-programs/dependencies.md)
* [Reports](https://help.easyagile.com/easy-agile-programs/reports.md)
* [Milestones](https://help.easyagile.com/easy-agile-programs/milestones.md)
* [PI Objectives](https://help.easyagile.com/easy-agile-programs/objectives.md)
* [Scrum and sprints](https://help.easyagile.com/easy-agile-programs/sprints.md)
* [Estimation and capacity](https://help.easyagile.com/easy-agile-programs/estimations.md)
* [Kanban Boards](https://help.easyagile.com/easy-agile-programs/kanban-boards.md)
* [Confidence Voting](https://help.easyagile.com/easy-agile-programs/confidence-voting.md)
* [Customizing card layout](https://help.easyagile.com/easy-agile-programs/customising-issue-cards.md)
* [Beyond Essential SAFe](https://help.easyagile.com/easy-agile-programs/beyond-essential-safe.md)
---
language: "en"
---
# How to Raise a Feature Suggestion
 Have an idea for our app?
Send through your suggestion to our Product Team via support. [Click here to start a request](https://arijea.atlassian.net/servicedesk/customer/portal/2/group/2/create/30).
---
language: "en"
---
# How to raise a support request
## How to contact Easy Agile support
For support with Easy Agile Programs, you can [raise a support request here](https://arijea.atlassian.net/servicedesk/customer/portal/2).
Please share screenshots, troubleshooting information and anything else that you think might help us to solve your issue quickly.
## Gathering in-app troubleshooting information
When raising a problem with our support team, we can use troubleshooting information generated in-app to get a quick overview of how the app is working.
This is located in the in-app help menu in Easy Agile apps. Access this in the "..." menu "Help" option.
Clicking on the  Info icon in the top right of this shows the following Support information. **Copy and paste this to share it with our support team!**
## Collecting Jira Data Center / Server Log Files
Sometimes we'll need to analyse log files from your Jira site to diagnose issues with Easy Agile Programs.
These steps will need to be performed by your Jira Administrator.
1. Navigate to **Logging and profiling** found under the system tab of the Jira Administration screen.
2. Scroll down to **Default Loggers** and click **Configure logging level for another package**
3. In the dialog enter the package name **com.easyagile.programs** and set the logging level to **DEBUG**
4. Navigating back to Easy Agile Programs, perform the actions that trigger your error. In the case of a custom field not being updated, navigate to one of your Team Planning Boards and move an issue in and out of the Increment - this can be achieved by moving an issue from the backlog into one of the Team's sprints and then moving it back into the Backlog panel. Then open the issue and verify that the field has not been set.
5. Your Jira Administrator will then need to locate your log file, which is typically called atlassian-jira.log and is located in your [Jira server home directory](https://confluence.atlassian.com/adminjiraserver071/jira-application-home-directory-802593036.html) (please note: if the Jira home directory is not configured, then the logs will be placed into the current working directory instead).
6. We're interested in the log entries related to Easy Agile Programs which will be logged under the **com.easyagile.programs** namespace. Please remove any unrelated or sensitive information from the log before sending it back to us.
*** ** * ** ***
## Other kinds of troubleshooting information
For more information on accessing the Javascript console, obtaining HAR files, or clearing browser cache, see the [Easy Agile Support general troubleshooting information page](https://help.easyagile.com/easy-agile-support/troubleshooting-information.md).
---
language: "en"
---
# Integrations
* [Jira integration](https://help.easyagile.com/easy-agile-programs/jira-integration.md)
* [Easy Agile Programs API](https://help.easyagile.com/easy-agile-programs/easy-agile-programs-api.md)
* [eazyBI](https://help.easyagile.com/easy-agile-programs/eazybi.md)
Do you use an app that you wish we had a better integration with? [Reach out to us via support](https://arijea.atlassian.net/servicedesk/customer/portal/2/group/2/create/30) to let us know.
---
language: "en"
---
# Jira integration
## How does Easy Agile Programs work with Jira?
The Easy Agile Programs app lives *within* Jira:
*Learn more about* [*Finding the Easy Agile Programs app in Jira*](https://help.easyagile.com/easy-agile-programs/navigate-to-your-program.md)*.*
When using the app, your Jira data is fetched "live" when you load the page. Changes you make are saved back directly to Jira.
**This means the app doesn't maintain a synchronized "copy": it displays and updates your real data in real-time.**
This Jira data includes:
* issues and epics from your Jira boards
* fields on those issues such as dates, estimates, and issue links
* quick filters and sprints from Scrum boards
* two new custom fields "Program" and "Program Increment"
[*Learn more about how the app securely integrates with your Jira site here*](https://help.easyagile.com/easy-agile-programs/programs-secure-jira-integration.md)*.*
## What Jira data can you use in Easy Agile Programs?
### Jira boards
**Each team in Easy Agile Programs is represented by a Jira board.**
* The Team backlog panel shows items from that team's Jira backlog/board.
* [Scrum teams can synchronize work with Jira by selecting a set of sprints for an Increment](https://help.easyagile.com/easy-agile-programs/sprints.md).
For more information, see [What is a "team" in Easy Agile Programs? Configuring Jira Boards](https://help.easyagile.com/easy-agile-programs/what-is-a-team-in-easy-agile-programs-configuring-.md).
Each [team board](https://help.easyagile.com/easy-agile-programs/what-is-a-team-in-easy-agile-programs-configuring-.md) in a Program has a [**Team planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md) for each Increment. Teams can use this page to schedule and manage the work they do in Jira.
**You can also select a dedicated Jira board for your Program Roadmap.** Alternatively, you may choose to use Jira epics from your Team boards for this.
[The *Roadmap issue source* is configured](https://help.easyagile.com/easy-agile-programs/create-a-program.md#3.-Choose-issues-for-your-roadmap-with-the-Roadmap-issue-source)[when](https://help.easyagile.com/easy-agile-programs/create-a-program.md#3.-Choose-issues-for-your-roadmap-with-the-Roadmap-issue-source)[creating a Program](https://help.easyagile.com/easy-agile-programs/create-a-program.md#3.-Choose-issues-for-your-roadmap-with-the-Roadmap-issue-source). You can choose either the Jira epic issue type, or any issue type.
For detailed information, see [Configuring the Roadmap issue source](https://help.easyagile.com/easy-agile-programs/configuring-the-roadmap-issue-source.md).
*Learn more about boards in* [*Jira Cloud*](https://support.atlassian.com/jira-software-cloud/docs/what-is-a-jira-software-board/)*or in* [*Jira Data Center*](https://confluence.atlassian.com/jirasoftwareserver/what-is-a-board-938845235.html)*.*
### Issue links
Easy Agile Programs uses an issue link type to represent **dependencies between issues**.
By default, the app uses the "blocks" / "is blocked by" issue link type for dependency lines. You can change which issue link type is used when [creating or editing a Program](https://help.easyagile.com/easy-agile-programs/create-a-program.md).
*Learn more about* [*Dependencies: visualizing links between items*](https://help.easyagile.com/easy-agile-programs/dependencies.md)*.*
### Date fields
To help build your roadmap, **you can optionally configure Easy Agile Programs to synchronize with date fields on your Jira issues**. This means that:
* issues with dates in an Increment will show in that Increment in the app; and
* scheduling issues on the roadmap updates the date fields in Jira.
This will apply to the issues from the [*Roadmap issue source*](https://help.easyagile.com/easy-agile-programs/configuring-the-roadmap-issue-source.md) configured for your Program.
For more information on configuring date synchronization, see [Date syncing with native Jira date fields](https://help.easyagile.com/easy-agile-programs/date-syncing-with-native-jira-date-fields.md).
**This can help if you're also using** [**Plans for Jira Cloud Premium**](https://support.atlassian.com/jira-software-cloud/docs/what-is-advanced-roadmaps/)or [Advanced Roadmaps for Jira Data Center](https://confluence.atlassian.com/jirasoftwareserver/discover-advanced-roadmaps-for-jira-1044784153.html)! By configuring Easy Agile Programs to use the same dates fields as Plans / Advanced Roadmaps, you can rely on your Jira date fields as a single source of truth.
### Sprints
Each Increment in Easy Agile Programs is made of a set of sprints from Jira. When creating an Increment, you can choose either:
* one set of sprints from one Scrum board, shared by all the teams; or
* each Scrum team can select a set of sprints from their own board.
For more information, see [Configuring sprint sync for an Increment](https://help.easyagile.com/easy-agile-programs/configuring-sprint-sync-for-an-increment.md) or [Scrum and sprints](https://help.easyagile.com/easy-agile-programs/sprints.md).
### Estimates
Scrum teams who use story points can see and add estimates on the [**Team Planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md).
For more information, see [Estimation](https://help.easyagile.com/easy-agile-programs/estimations.md).
### Custom fields
Easy Agile Programs creates and manages two new custom fields "Program" and "Program Increment". These can be used for reporting with other tools, such as Eazy BI and Power BI.
For more information, see [Programs Custom Fields](https://help.easyagile.com/easy-agile-programs/programs-custom-fields.md).
---
language: "en"
---
# Kanban Boards
Easy Agile Programs supports Kanban boards so you can create alignment across your Scrum and Kanban teams.
When viewing the Team Planning Board for a Kanban team, you will see sprint columns just like Scrum boards. These "sprints" are for visualisation purposes only and do not represent real sprints on your Jira board.
We recommend planning Kanban team's work into these columns if you have dependencies with other teams so that estimated timeframes can be visualised and potential risks can be discussed.
Estimations and capacity management is not available for Kanban boards. See more details on why we don't support estimations [on this page](https://help.easyagile.com/easy-agile-programs/estimations.md).
**What does/doesn't sync back to Jira for kanban boards?**
Scheduling kanban issues on the team planning board will not change which status column it is shown in on your Jira backlog.
If you change the order of issues on our team planning screen then the order of issues on your backlog will be changed.
If you change any details about a kanban issue in Easy Agile Programs i.e. issue summary, status, assign then it will be automatically reflected in Jira (the same goes for issues on scrum boards).
Note: Currently, Kanban team-managed boards are not compatible with Easy Agile Programs if you're using shared/global sprints. For more information [check out our section on team-managed projects.](https://help.easyagile.com/easy-agile-programs/team-managed-projects-next-gen.md)
---
language: "en"
---
# Migrating Easy Agile Programs with JCMA
**Easy Agile Programs data migrates with the** [**Jira Cloud Migration Assistant (JCMA)**](https://support.atlassian.com/migration/docs/use-the-jira-cloud-migration-assistant-to-migrate/)**.**
If you're migrating from an on-premise (Server or Data Center) Jira site to Cloud, [Atlassian recommends using JCMA](https://support.atlassian.com/migration/docs/cloud-migration-methods-for-jira/).
When the app is included in a JCMA migration, Program data for the migrated Jira projects will automatically be migrated.
Migrating to Cloud? [Learn more about how Easy Agile keeps your data secure here](https://help.easyagile.com/easy-agile-programs/security-privacy.md).
## Pre-requisites
To include Easy Agile Programs in a JCMA migration, you'll need:
* Easy Agile Programs updated to the [latest version](https://marketplace.atlassian.com/apps/1219491/easy-agile-programs-pi-planning-program-board-dependencies/version-history) on the origin Server / Data Center site
* Easy Agile Programs is installed in the Cloud instance.
[You may be eligible for a discounted license to facilitate your migration](https://help.easyagile.com/easy-agile-support/app-licensing-and-pricing.md#Licensesanddiscountsformigrations).
**Expired app license on Jira Server?** You can still [download the latest (Data Center) version of the app from the Atlassian Marketplace](https://marketplace.atlassian.com/apps/1219491/easy-agile-programs-pi-planning-program-board-dependencies/version-history), and upload this to your Jira Server site.
The app will show an "Unlicensed" page when using a version your license does not include access to. However, **the JCMA integration will still work without an eligible license**.
## How does it work?
1. Update the Easy Agile Programs and JCMA apps to the latest version.
* Easy Agile Programs versions **prior to v8.5.0**do not integrate with JCMA.
2. During the [Assess your apps](https://support.atlassian.com/migration/docs/assess-apps-with-the-jira-cloud-migration-assistant/) stage, select "Needed in Cloud" for Easy Agile Programs.
3. Follow the steps on [how to use the Jira Cloud Migration Assistant](https://support.atlassian.com/migration/docs/use-the-jira-cloud-migration-assistant-to-migrate/) to migrate data to your Cloud instance.
4. App data associated with your migrated Jira data will be migrated as one of the last steps in the JCMA migration.
### Limitations
* Sprint capacities entered on the [Team planning](https://help.easyagile.com/easy-agile-programs/team-planning-board.md) page and [Confidence votes](https://help.easyagile.com/easy-agile-programs/confidence-voting.md) are not currently migrated.
* [Team swimlane allocation](https://help.easyagile.com/easy-agile-programs/team-swimlane-allocation.md) settings are not currently migrated. After migrating, open Edit Program and set up the mapping again.
* As of 18 Jan 2024, customers have been able to initiate a cancellation of an app migration with version 1.10.10 of JCMA. This is currently not supported by Easy Agile Programs.
### Which Programs will be migrated with my selected Jira projects?
Easy Agile Programs can only migrate a Program if the Jira data for that Program is found on the destination Jira Cloud site. Each Program is configured to use a set of Jira boards; you'll need to migrate these Jira projects and boards to migrate the whole Program to Jira Cloud.
| **Projects included in a migration** | **Outcome in Easy Agile Programs for Jira Cloud** |
|------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|
| All Jira projects on Jira | All Programs will appear in Jira Cloud as they did in Jira Server/DC. |
| All Jira projects in a Program (minimum recommended) | That Program will appear in Jira Cloud as it was in Jira Server/DC; other Programs will not be migrated. |
| Some of the Jira projects in a Program | That Program will be migrated, but only contain the migrated Jira boards; some teams/boards will be missing. |
| No Jira projects that appear in any Programs | No Programs will be migrated. |
### Staged migrations
**We recommend migrating the relevant Jira projects AND Easy Agile Programs in the same migration.**
If more than one of your migrations will include Jira projects used in Easy Agile Programs, you'll need to include Easy Agile Programs in each of those migrations.
If you are planning a staged migration, **we recommend enabling Easy Agile Programs for** ***all*** **migrations**. This allows it to migrate the app data associated with the Jira projects in each migration. The app does not need a separate migration.
It's safe to include Easy Agile Programs in every migration. It will not create duplicates, and will automatically skip already-migrated data.
## Troubleshooting an Easy Agile Programs JCMA migration
Check what version of Easy Agile Programs was installed on the origin Jira Server / Data Center site during the migration. If you're not using the [latest version](https://marketplace.atlassian.com/apps/1219491/easy-agile-programs-pi-planning-program-board-dependencies/version-history), this may cause problems with the migration.
### App migration logs on Cloud
You can review the results of a migration of Easy Agile Programs data on the destination Jira Cloud site. This is available for Jira Administrators by navigating to:
1. Jira Cloud's global settings → "Manage Apps"
2. Then, in the left navigation pane under "Easy Agile Programs" → "Migration Assistant"
### Why is the migration "Successful", but not all Programs have appeared on the Cloud site
There are three main causes of this that will appear in the migration logs:
* The [*issue link type* for dependencies](https://help.easyagile.com/easy-agile-programs/configuring-dependencies-for-a-program.md) in the Program is missing from the Cloud site.
* The [*issue link type* used to connect team-level issues to the Program Roadmap](https://help.easyagile.com/easy-agile-programs/configuring-the-roadmap-issue-source.md#Any-issue-types-from-a-dedicated-board) is missing from the Cloud site.
* The [date fields used in the Program](https://help.easyagile.com/easy-agile-programs/date-syncing-with-native-jira-date-fields.md) are missing from the *Issue Screens* in the migrated Jira projects.
### Troubleshooting failed or stuck migrations
If app data is missing on the Cloud site, first check if the associated Jira data has been migrated successfully:
* Check that the [team and roadmap boards used in the Program](https://help.easyagile.com/easy-agile-programs/create-a-program.md#CreateandeditaProgram-2.Addyourteams) on the Server/DC site are available on the Jira Cloud site.
* Check that the Jira issues that were scheduled in the Program on the Server/DC site can be found in the matching Jira projects on the Jira Cloud site.
* Check that the date fields and issue link types configured for the Program can be found on the Jira Cloud site.
*** ** * ** ***
## We are here for you!
Our team is here to help with your JCMA migration. If you have any questions or concerns, [please contact our support team](https://arijea.atlassian.net/servicedesk/customer/portal/2/group/97/create/266?customfield_12467=11013)!
---
language: "en"
---
# Migrating Easy Agile Programs
[Easy Agile Programs is available on Jira Cloud and Jira Data Center](https://marketplace.atlassian.com/apps/1219491/easy-agile-programs-pi-planning-program-board-dependencies?hosting=cloud&tab=overview). The app integrates with JCMA for automatic data migration to Jira Cloud. There is limited support for other migration pathways.
[There are discount programs available to help with licensing during migrations](https://help.easyagile.com/easy-agile-support/app-licensing-and-pricing.md#Licensesanddiscountsformigrations).
Migrating to Cloud? [Learn more about how Easy Agile keeps your data secure here](https://help.easyagile.com/easy-agile-programs/security-privacy.md).
## Migration pathways
### Migrating to Cloud with JCMA
If you're migrating from an on-premise (Server or Data Center) Jira site to Cloud, Atlassian recommends using JCMA. The [Jira Cloud Migration Assistant (JCMA)](https://support.atlassian.com/migration/docs/use-the-jira-cloud-migration-assistant-to-migrate/) app enables automated data migration from Jira Server or Data Center to Jira Cloud.
* [Compare Atlassian-recommend migration methods here](https://support.atlassian.com/migration/docs/choose-a-cloud-migration-method/).
**Easy Agile Programs integrates with JCMA to automatically migrate app data alongside your Jira data.**
See [Migrating Easy Agile Programs with JCMA](https://help.easyagile.com/easy-agile-programs/migrating.md) for full details.
This is the only migration pathway that is supported at this time.
### Upgrading from Jira Server to Jira Data Center
If you're [upgrading your existing Jira Server site to Jira Data Center](https://confluence.atlassian.com/enterprise/migrate-from-server-to-data-center-953127136.html), you won't need to migrate data.
In this situation, [you only need to replace the app license with a new Data Center app license](https://confluence.atlassian.com/enterprise/upgrading-server-apps-when-you-migrate-to-data-center-998660310.html).
* The Data Center version of the app works identically to the Server version, and also includes support for multi-node Data Center sites.
* The Data Center version of the app can be used on a Jira Server site. Note that newer versions of Easy Agile Programs are not compatible with older versions of Jira: [check version compatibility here](https://marketplace.atlassian.com/apps/1219491/easy-agile-programs-pi-planning-program-board-dependencies/version-history).
### Unsupported migration paths
The app does not integrate with other migration tools such as:
* Atlassian's [Site import \[discontinued\]](https://community.atlassian.com/forums/Atlassian-Migration-Program/Streamlining-Data-Migrations-amp-Discontinuing-Site-Import/ba-p/2359542)
* Atlassian's [Copy product data](https://support.atlassian.com/organization-administration/docs/copy-product-data/)
* Third-party apps, such as those provided by other [Atlassian Marketplace](https://marketplace.atlassian.com/) Partners
For full information about limits with other migration pathways, see [Unsupported migration pathways for Easy Agile Programs](https://help.easyagile.com/easy-agile-programs/unsupported-migration-pathways-for-programs.md).
## Feature parity between Cloud and DC / Server
Cloud and Data Center / Server versions of the app are as similar as possible.
For full information on feature parity/differences, see [Easy Agile Programs Cloud / Data Center differences](https://help.easyagile.com/easy-agile-programs/programs-cloud-data-center-differences.md).
## Contact us for assistance!
If you have any questions or concerns about your migration, [please contact our support team](https://arijea.atlassian.net/servicedesk/customer/portal/2/group/97/create/266?customfield_12467=11013)!
---
language: "en"
---
# Milestones
Milestones can be added to your Program to clearly represent important dates to business stakeholders or the team, such as demos, release and launch dates, external events, or third-party deliverables.
## Visualizing milestones
Milestones are shown on the [**Program roadmap**](https://help.easyagile.com/easy-agile-programs/program-roadmap.md)[page](https://help.easyagile.com/easy-agile-programs/program-board.md):
On the [**Program board** page](https://help.easyagile.com/easy-agile-programs/program-board.md), Milestones are shown below the sprint headers. Use "Show milestones" / "Hide milestones" to expand or collapse this row.
## Managing Milestones
Users with [**Manage Programs** permission](https://help.easyagile.com/easy-agile-programs/permissions.md#The%25E2%2580%259CManagePrograms%25E2%2580%259Dpermission) can create, edit or delete Milestones on the [**Program roadmap**](https://help.easyagile.com/easy-agile-programs/program-roadmap.md) or [**Program board**](https://help.easyagile.com/easy-agile-programs/program-board.md) pages.
### Creating a Milestone
Find the "+Milestone" button in the top right-hand corner of the [**Program roadmap**](https://help.easyagile.com/easy-agile-programs/program-roadmap.md)[page](https://help.easyagile.com/easy-agile-programs/program-board.md):
On the [**Program board** page](https://help.easyagile.com/easy-agile-programs/program-board.md), find the "+ Add milestone" button at the right-hand end of the Milestones row:
### Editing or deleting a Milestone
Click on any Milestone name to edit any details, or delete the Milestone permanently.
---
language: "en"
---
# Finding the Easy Agile Programs app in Jira
There are two ways to access Easy Agile Programs: from the top-level navigation bar, or from your team's Jira board.
## Jira global navigation
This option is only available for users with [**Manage Programs** permission](https://help.easyagile.com/easy-agile-programs/permissions.md#The%25E2%2580%259CManagePrograms%25E2%2580%259Dpermission). The app will be in the "Boards" or "Apps" dropdown, depending on your Jira hosting.
This will open the [**Program list** page](https://help.easyagile.com/easy-agile-programs/program-list.md).
On**Jira Cloud**, find Programs in the "Apps" section of the main navigation panel.
[*Jira Cloud navigation has recently changed*](https://support.atlassian.com/jira-software-cloud/docs/what-is-the-new-navigation-in-jira/)*. If you're still seeing the old experience, you'll find the "Apps" dropdown in the navigation bar at the top of the page.*
On **Jira Data Center**, open the Boards dropdown to find the "View all programs" link.
Can't see this option? You might be missing the [**Manage Programs** permission](https://help.easyagile.com/easy-agile-programs/permissions.md#The%25E2%2580%259CManagePrograms%25E2%2580%259Dpermission).
## From your team's Jira board
After a board is added as a [*Team board*](https://help.easyagile.com/easy-agile-programs/what-is-a-team-in-easy-agile-programs-configuring-.md) to a Program, you will be able to access the app from that board in Jira.
On **Jira Cloud**, Programs will be added to the project row:
Programs tab missing?
If the "Programs" option is missing from the tab row:
|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Check the "More" dropdown for project tabs that don't fit on your screen. |  |
| Use the + "Plus" button to add the tab to the project, or ask a Project Admin to do so. ⚙️ Only users with Project Administrator or Jira Administrator permissions can reorder or add project tabs. |  |
On **Jira Data Center**, find Programs in the project sidebar on the left of the page.
If this board is the [dedicated roadmap board](https://help.easyagile.com/easy-agile-programs/configuring-the-roadmap-issue-source.md) for a Program (not a Team board), Programs won't appear in the project bar.
If you'd like to see this functionality in the future, please [let us know](https://arijea.atlassian.net/servicedesk/customer/portal/2/group/2/create/30)!
If your team board is in more than one Program, you'll then be asked to select one of the Programs/Increments for the board:
## FAQs
### \[Jira Data Center only\] Why don't I see the "View all Programs" option in the Boards dropdown?
"View all Programs" in the Boards dropdown is only visible to users with [**Manage Programs**](https://help.easyagile.com/easy-agile-programs/permissions.md#The%25E2%2580%259CManagePrograms%25E2%2580%259Dpermission) or **Jira Administrator** permission.
If you don't have this permission but you're on a team board for a Program, you can navigate to the app from the Project sidebar (as described above).
---
language: "en"
---
# PI Objectives
PI Objectives are a key output of PI Planning in SAFe and can be recorded directly within Easy Agile Programs.
Create and manage PI Objectives for each team on the [**Team planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md).
[Track the progress on all Objectives in an Increment on the Reports page](https://help.easyagile.com/easy-agile-programs/objectives-report.md).
## Creating a PI Objective
Use the 🏆 "Team PI Objectives" button on the [**Team planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md) to create new Objectives.
⚙️
Users with any of the following permissions can create and edit Objectives:
* [**Manage Programs** permission](https://help.easyagile.com/easy-agile-programs/permissions.md#The%25E2%2580%259CManagePrograms%25E2%2580%259Dpermission)
* Jira Administrator
* Board Administrator
In earlier versions (Data Center v4.6.0-5.4.0), Objectives were displayed as a row at the **top** of the Team planning page, rather than the current side panel.
From the modal, you can:
* Name the objective
* Select whether it is committed or uncommitted
* Link relevant issues that have been scheduled into the Increment
* Provide a description for the objective
* Assign business value
The PI Objective drawer can be opened/closed to show/hide all the team PI Objectives for the increment.
### Committed vs Uncommitted PI Objectives
Easy Agile Programs, allows you to add both committed and uncommitted objectives.
It is recommended in SAFe that [committed objectives](https://www.scaledagileframework.com/pi-objectives/#:~:text=usage%20and%20value.)-,Committed%20and%20Uncommitted%20Objectives,-Committing%20to%2C%20and) are those that the team is confident in delivering within the PI. The planned business value for committed objectives is used to calculate the Program Predictability Score (*coming in a future release*).
Only the business value for committed objectives is used to calculate the total planned value.
[Uncommitted objectives](https://www.scaledagileframework.com/pi-objectives/#:~:text=usage%20and%20value.)-,Committed%20and%20Uncommitted%20Objectives,-Committing%20to%2C%20and) can be used when work is planned, but the outcome is not certain. Teams can use uncommitted objectives whenever there is low confidence in meeting the objective.
*More information on Committed vs Uncommitted Objectives can be found on the* [Scaled Agile website](https://www.scaledagileframework.com/pi-objectives/#:~:text=usage%20and%20value.)-,Committed%20and%20Uncommitted%20Objectives,-Committing%20to%2C%20and)*.*
### Plan vs Actual Value
During PI Planning, Business Owners assign 'plan value' to each of the PI objectives.
Business value serves as a guide to the importance of an objective with 1 = lowest value and 10 = highest value to the business.
As part of or before the [PI system demo](https://www.scaledagileframework.com/inspect-and-adapt/#:~:text=attend%20this%20event.-,PI%20System%20Demo,-The%20PI%20System), Business Owners come together again with the agile teams to assign actual business value based on what was delivered.
Easy Agile Programs allows Business Owners to assign both the plan value and actual value directly to the PI Objective using the modal or inline edit on the Team planning page.
### Linking issues to the Objective
You can link issues scheduled within the Increment to the PI Objective for greater visibility and tracking. Once issues have been linked to a PI Objective, you can filter by one or more objectives to see related issues within the plan.
## Filtering by PI objectives
In the PI Objectives panel, Switch to the "Filter by objective" tab to filter the current view by Objective.
Select one or more Objectives to see the linked issues.
## Editing a PI Objective
Click on the objective name to open the edit modal.
You can add 'actual value' from this modal, along with all other fields listed shown in the dialog.
## Deleting a PI Objective
Open the edit modal and click (...) menu to delete a PI Objective.
## Reporting on Objectives
### In-app Objectives Report
Track the progress on all Objectives in an Increment on the Reports page.
**See** [**Objectives report**](https://help.easyagile.com/easy-agile-programs/objectives-report.md)**for more information.**
From the [**Team planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md), jump directly to the Objectives report from the "View progress" button.
### \[Data Center only\] Tracking issues linked to Objectives
A hidden issue property "EAP-team-objectives" is added to issues linked to an Objective.
While this isn't visible on the issue in Jira, you can use it to search for the issues with [JQL searches](https://www.atlassian.com/software/jira/guides/jql/overview) like:
* `issue.property[EAP-team-objectives].tags IS NOT EMPTY`
* `issue.property[EAP-team-objectives].tags ~ "p_{programId}"`
* `issue.property[EAP-team-objectives].tags ~ "i_{incrementId}"`
* `issue.property[EAP-team-objectives].tags ~ "b_{boardId}"`
* `issue.property[EAP-team-objectives].tags ~ "o_{objectiveId}"`
This allows you to filter by these issues for dashboards and other reporting that uses JQL.
Example
For example, the following query finds all issues linked to any Objectives that team "Billing platform" (board ID 7) has in Increment "PI 3 2023: Launch" (ID 299).
`issue.property[EAP-team-objectives].tags ~ "b_7" AND issue.property[EAP-team-objectives].tags ~ "i_299"`
You can see the Increment and team board ID numbers in the URL when visiting the Team planning page, e.g: /plugins/servlet/eap/increment/**299** /team/**7**
### \[Data Center only\] Fetching Objectives by API
Objectives for a team board and Increment are accessible through the app's API. See [Easy Agile Programs API](https://help.easyagile.com/easy-agile-programs/easy-agile-programs-api.md#GetTeamPIObjectives) for more details.
Note that the linked Jira issues are not returned from the API.
---
language: "en"
---
# Objectives report
**The Objectives report is available:**
* on Jira Cloud (i.e. Jira sites with "....atlassian.net" in the URL)
* on Jira Data Center with app version 8.3.0+; [a Jira Administrator can install the latest version](https://confluence.atlassian.com/upm/updating-apps-273875710.html).
Use the Objectives report to see and track all the [Team PI Objectives](https://help.easyagile.com/easy-agile-programs/objectives.md) in an Increment.
## Tracking objective progress
The progress of an objective is calculated based on the Jira issues linked to it.
* If the linked issue is an epic/feature on your roadmap and it has child issues, the progress will be calculated using the progress of the child issues.
Linked issues are configured when creating or editing an Objective:
You can also filter by objective on the Team planning page to see the linked issues to track progress:
### Status tracking
Available on Jira Cloud only. Please [reach out](https://arijea.atlassian.net/servicedesk/customer/portal/20/create/992) if you'd like this functionality on Data Center.
Use the **Tracking status** dropdown on each objective row to record how that objective is progressing. Select from seven statuses: Off track at risk on track pending Paused Completed cancelled
If no status has been set, the row shows a "Choose status" dropdown. Statuses are saved automatically and will persist the next time you open the report.
The report can be filtered by the statuses to focus in on the objectives that need the most attention.
### Business value
Available on Jira Cloud only. Coming in the next Data Center release (v9.1.0)
The Objectives report shows the planned and actual business value for each objective.
For each objective:
* **Plan** - business value assigned during PI Planning
* **Actual** - business value assigned after the system demo, based on what was delivered
The business value section appears when at least one objective in the report has a planned or actual value entered. If your team doesn't use business value scoring, the section won't appear.
 If you expect to see business value but the section isn't showing, check that at least one objective has a value entered in the **Plan** or **Actual** field - this can be done on the [Team Planning](https://help.easyagile.com/easy-agile-programs/team-planning-board.md) screen (these values are read-only on the report). See [PI Objectives](https://help.easyagile.com/easy-agile-programs/objectives) for more details on how to add or update business value.
An objective with no value shows a dash (-).
An objective explicitly scored at 0 shows as 0.
## Creating and managing Objectives
To create, edit, or delete an Objective, you'll need to switch to the relevant [**Team planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md).
Click the team board name to jump directly to the right page, with the PI Objectives panel already open.
Click the team name to jump to the [**Team planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md).
[Learn more about managing PI Objectives here](https://help.easyagile.com/easy-agile-programs/objectives.md).
## Configuring the Objectives report
Select a Program and Increment to see the Objectives for that Increment:
If you were already viewing a Program/Increment, these will automatically be selected when you open the Report.
### Filtering
The Objectives report can be filtered by team, commitment type, and status.
**Team filtering**
Select a set of teams to view only the Objectives from those teams.
This will be reflected in the page URL, so you can share a link directly to this set of teams and their objectives.
**Commitment type**
Filter by commitment type to hide uncommitted objectives.
**Status**
Filter by one or more statuses to focus on the objectives that need the most attention.
Status tracking is currently available in Cloud only. Please [reach out](https://arijea.atlassian.net/servicedesk/customer/portal/20/create/992) if you'd like this functionality on Data Center.
## Troubleshooting the Objectives report
Check that you can view the team and its Objectives on the [Team planning page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md).
If you do not have access to view a team's board in Easy Agile Programs or in Jira, Objectives from that team will be missing from the report.
### "Add your first team objective!"
This message will show if there are no Objectives in this Increment yet for any of the *selected* team boards.
There may be Objectives for other team boards, if you have filtered out some teams.
## Export the report
Exporting reports is available:
* on Jira Cloud (i.e. Jira sites with "....atlassian.net" in the URL)
* on Jira Data Center with app version 8.4.2+; [a Jira Administrator can install the latest version](https://confluence.atlassian.com/upm/updating-apps-273875710.html).
Use the the "export"/"download" button to generate a downloadable PNG of the report, using the currently-selected Program, Increment and Teams. The PNG export reflects the full live report - including the Business value section if it's shown on screen.
This can be added to other documents or reports for stakeholders who can't access the live report personally.
## \[Data Center only\] Reporting on Objectives with JQL
If you're using the app on Jira Data Center, you can also search for issues linked to Objectives with the hidden `issue.property[EAP-team-objectives]`. See [Tracking issues linked to Objectives](https://help.easyagile.com/easy-agile-programs/objectives#Objectives-[DataCenteronly]TrackingissueslinkedtoObjectives) for details.
---
language: "en"
---
# Permissions for Easy Agile Programs
Easy Agile Programs adds a global "Manage Programs" permission to Jira. Access is otherwise managed using existing Jira permissions: it's only possible to view/edit Jira data in Easy Agile Programs where the same could be done in Jira.
## Permissions used in Easy Agile Programs
| **Functionality (user action)** | **Permission required** |
|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| **Admin tasks** ||
| * Install app * Install app updates (manual app updates required on Jira Data Center only) | On Cloud: [Organization Admin OR Site Admin](https://support.atlassian.com/user-management/docs/what-are-the-different-types-of-admin-roles/) On Data Center: **Jira Administrator** |
| * [Delete a Program](https://help.easyagile.com/easy-agile-programs/create-a-program.md#CreateandeditaProgram-DeleteaProgram) * Grant "Manage Programs" permission and Jira permissions to other users | **Jira Administrator** |
| * Open Easy Agile Programs main ["Program List" page](https://help.easyagile.com/easy-agile-programs/navigate-to-your-program.md#TheProgramList) * [Create/Edit a Program](https://help.easyagile.com/easy-agile-programs/create-a-program.md) * [Create/Edit/Delete an Increment](https://help.easyagile.com/easy-agile-programs/create-and-edit-a-program-increment.md) * [Edit the Program roadmap with drag-and-drop](https://help.easyagile.com/easy-agile-programs/scheduling-issues-from-the-roadmap-backlog) * [Create/edit/delete Milestones](https://help.easyagile.com/easy-agile-programs/milestones.md) | **Manage Programs** (a Global Permission added by the app) or **Jira Administrator** |
| * Grant board access to other users | Edit access for the board's Filter, or use **Board Administrator** to switch to a different Filter |
| **Contributor tasks** 🔑 You can only change Jira data in Easy Agile Programs if you can do the same in Jira. ||
| * [Navigate to a Program](https://help.easyagile.com/easy-agile-programs/navigate-to-your-program.md) * Add/see [Confidence Votes](https://help.easyagile.com/easy-agile-programs/confidence-voting.md) | View permission for at least 1 of the [Jira boards used in the Program](https://help.easyagile.com/easy-agile-programs/what-is-a-team-in-easy-agile-programs-configuring-) (controlled by "View" permission on the Filter for the board) |
| * See/edit issues in Programs | See/edit the issues in Jira (**Browse projects** and other Project permissions) |
| * See/use a team board in Programs * See [PI Objectives](https://help.easyagile.com/easy-agile-programs/objectives.md) | View board (controlled by "View" permission on the Filter for the board) |
| * See the roadmap in Programs (if your roadmap is configured with a "dedicated board") | View board (controlled by "View" permission on the Filter for the board) |
| * Contribute to roadmap-level plans | EITHER: * **Manage Programs** to open the [Edit Roadmap](https://help.easyagile.com/easy-agile-programs/scheduling-issues-from-the-roadmap-backlog) page and schedule issues with drag-and-drop * If [date syncing](https://help.easyagile.com/easy-agile-programs/date-syncing-with-native-jira-date-fields) is configured for Program: edit date fields on issues in Jira that are in the [Roadmap issue source](https://help.easyagile.com/easy-agile-programs/configuring-the-roadmap-issue-source) board(s) |
| * [Enter/edit sprint capacity](https://help.easyagile.com/easy-agile-programs/estimations.md#Sprintcapacity) | **Manage Sprints** or **Edit Sprints** Project permission (for *all* projects with issues in that sprint) |
| * Create [PI Objectives](https://help.easyagile.com/easy-agile-programs/objectives.md) | EITHER: * **Manage Programs** * **Board Administrator** for that team board |
## The "Manage Programs" permission
Easy Agile Programs adds one global permission **Manage Programs** to Jira. This determines who can:
* [Find the app in the top-level "Apps" or "Boards" dropdown](https://help.easyagile.com/easy-agile-programs/navigate-to-your-program.md#TopNavigation)
* View the [Program List](https://help.easyagile.com/easy-agile-programs/navigate-to-your-program.md#TheProgramList)
* Create/edit [Program](https://help.easyagile.com/easy-agile-programs/create-a-program.md) configuration
* Create/edit/delete [Increment](https://help.easyagile.com/easy-agile-programs/create-and-edit-a-program-increment.md) configuration
* [Schedule issues on the roadmap with drag and drop](https://help.easyagile.com/easy-agile-programs/scheduling-issues-from-the-roadmap-backlog)
* Create/edit/delete [Milestones](https://help.easyagile.com/easy-agile-programs/milestones.md)
Users with Jira Administrator permission can also perform actions requiring **Manage Programs**.
Jira Administrators can grant **Manage Programs** permissions in [Jira Cloud](https://support.atlassian.com/jira-cloud-administration/docs/manage-global-permissions/) or [Jira Data Center](https://confluence.atlassian.com/adminjiraserver/managing-global-permissions-938847142.html).
In Jira, global permissions can only be applied to a *user group* . This means that you'll need to use or create a group in Jira to grant **Manage Programs** permission.
For example, you might create a new user group named "Program Managers".
On Data Center and Server versions 5.2.1 and earlier, users with **Manage Programs** permission can also **delete** Programs.
From 5.3.0 and later (as well as on Jira Cloud), only users with Jira Administrator permissions can delete a Program.
## Jira permissions
Check the documentation below for your version of Jira to learn more about configuring Jira permissions:
| **Permission type** | **Cloud** | **Data Center** |
| **Global permissions, including Manage Programs** | [Manage global permissions](https://support.atlassian.com/jira-cloud-administration/docs/manage-global-permissions/) | [Managing global permissions](https://confluence.atlassian.com/adminjiraserver/managing-global-permissions-938847142.html) |
| **User groups** | [Create and update groups](https://support.atlassian.com/jira-cloud-administration/docs/create-and-update-groups/) | [Managing groups](https://confluence.atlassian.com/adminjiraserver/managing-groups-938847035.html) |
| **Project permissions** | [Permissions for company-managed projects](https://support.atlassian.com/jira-cloud-administration/docs/permissions-for-company-managed-projects/) [Manage project permissions](https://support.atlassian.com/jira-cloud-administration/docs/manage-project-permissions/) | [Managing project permissions](https://confluence.atlassian.com/adminjiraserver/managing-project-permissions-938847145.html) |
| **Board administration** | [How do Jira permissions work? \| Board administration](https://support.atlassian.com/jira-software-cloud/docs/how-do-jira-permissions-work/#Permissionsoverview-Boardadministration) | [Configuring a board](https://confluence.atlassian.com/jirasoftwareserver/configuring-a-board-938845252.html) |
| **Board Filter sharing** | [Manage filters \| Update permissions of a filter](https://support.atlassian.com/jira-software-cloud/docs/manage-filters/#Update-permissions-of-a-filter) | [Managing filters](https://confluence.atlassian.com/adminjiraserver/managing-filters-938847876.html) |
|---------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------|
## Restricting Easy Agile Programs to specific projects/users
### Block app access using a Data security policy on Jira Cloud
**On Jira Cloud**, Atlassian's new app access rules can prevent Easy Agile Programs from accessing or showing in specific Jira projects.
Multi-project boards can be used in Easy Agile Programs. You may encounter inconsistencies when some projects used in a board are blocked.
How Jira projects are used in Easy Agile Programs
Easy Agile Programs provides a view across multiple Jira boards: this is likely to include issues from multiple Jira projects. The Jira boards used in Easy Agile Programs might be single-project or multi-project boards.
* [Learn more about how Jira boards are used as "Team boards" in Easy Agile Programs](https://help.easyagile.com/easy-agile-programs/what-is-a-team-in-easy-agile-programs-configuring-.md).
This means that an App access Policy rule can result in a Jira board being *partially* missing from Easy Agile Programs.
* For example, a Jira board might contain projects "WEB" and "IOS" (e.g. board filter query `project IN (WEB, IOS) ORDER BY Rank ASC`). If project "WEB" has an App access Policy rule that blocks Easy Agile Programs, but IOS doesn't, then the app will only show the IOS issues from the board.
A Data security policy applied to a Jira project can cause missing issues on:
* The [Program Roadmap](https://help.easyagile.com/easy-agile-programs/schedule-features-epics-into-your-increment.md), and the Roadmap backlog
* Team-level issues planned in sprints on the [Team Planning page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md), and the Team backlog
* Issues that should be shown based on [date syncing](https://help.easyagile.com/easy-agile-programs/date-syncing-with-native-jira-date-fields.md) from the [*Roadmap issue source*](https://help.easyagile.com/easy-agile-programs/configuring-the-roadmap-issue-source.md) or [*Third-level issue source*](https://help.easyagile.com/easy-agile-programs/third-level-hierarchy.md)
This is configured using a [*Data security policy*](https://support.atlassian.com/security-and-access-policies/docs/what-is-a-data-security-policy/), which can be configured by an Organization Administrator. This allows you to select:
* The Jira projects you'd like to restrict access to; and
* The [*App access*](https://support.atlassian.com/security-and-access-policies/docs/block-app-access/)*Policy rule*.
If you have [Atlassian Access](https://support.atlassian.com/security-and-access-policies/docs/understand-atlassian-access/), you'll be able to choose which apps you block using an allowlist or a blocklist.
Otherwise, you'll only be able to block *all* apps. This means that using a *Block app access* rule to restrict Easy Agile Programs will block other apps as well.
If you can access an issue on the board in Jira, but can't access it in Easy Agile Programs, this could be caused by an App access Policy rule.
### Restricting user access to Easy Agile Programs
Users will only have access to the app when:
* They have **Manage Programs** permission; or
* A Jira board they have access to is added to a Program by a user with **Manage Programs** permission.
Please note that restricting which users can use the app does not affect [the user tier of the app license](https://help.easyagile.com/easy-agile-support/app-licensing-and-pricing.md#Pricingbyusertier).
---
language: "en"
---
# Programs app Demo
## Can I see a demo of Easy Agile Programs?
Yes! [See our on-demand demo here](https://www.easyagile.com/product-demo/easy-agile-programs).
We don't offer 1-to-1 demos at the moment. If you have specific questions, [please reach out to our team here](https://arijea.atlassian.net/servicedesk/customer/portal/2). We'll get back to you within 24 hours on business days!
## Is there a way to try Easy Agile Programs before installing an evaluation on my Jira site?
Yes! Please [visit our sandbox demo site here](https://demo.easyagile.com/demo/programs).
*Please note that this is a public demo instance. All data you enter will be publicly available to other users who access this URL. The instance will reset every 24 hours.*
---
language: "en"
---
# The Program board page
The **Program board** page shows a holistic view of all the plans for one Increment. Here, you can see how all teams' work relates to each other and your shared goals.
This page shows all levels of the hierarchy configured for your Program:
* [Third-level plans](https://help.easyagile.com/easy-agile-programs/third-level-hierarchy.md) (if configured)
* [Roadmap-level work](https://help.easyagile.com/easy-agile-programs/schedule-features-epics-into-your-increment.md) in **purple**
* [Team-level work for each team board in the Program](https://help.easyagile.com/easy-agile-programs/what-is-a-team-in-easy-agile-programs-configuring-.md)
* Use the "Show team level issues" switch in the Filters menu to show/hide team-level plans.
[Dependencies](https://help.easyagile.com/easy-agile-programs/dependencies.md) between all visible items are shown as color-coded lines. Open the [Dependencies map](https://help.easyagile.com/easy-agile-programs/dependency-map.md) to focus on dependency management.
Use the **Program board** for activities like:
* Aligning on and committing to shared plans, including [confidence voting](https://help.easyagile.com/easy-agile-programs/confidence-voting.md)
* Identifying and managing risks and dependencies
* Tracking progress and blockers, including in Scrum of Scrums
## Visualizing plans
### Sprint columns
The Program board is divided into columns representing the sprints in your Increment.
* Sprint dates are not synchronized with the sprints in Jira. Dates shown are calculated based on the [Increment start date and sprint length(s)](https://help.easyagile.com/easy-agile-programs/create-and-edit-a-program-increment.md#CreateandeditaProgramIncrement-Sprintmanagement).
* The names of the sprints from Jira will not be shown, even if all teams in the Increment share sprints.
[*Learn more about how sprints sync with Increments*](https://help.easyagile.com/easy-agile-programs/configuring-sprint-sync-for-an-increment.md).
Team-level items (e.g. stories, tasks) will be scheduled in one sprint/column.
Roadmap-level items can span multiple sprints.
If a roadmap item's dates extend before/after the Increment, the end of the item is shown as an arrow.
### Milestones
Milestones appear below the sprint dates:
Use "Show milestones" / "Hide milestones" to expand or collapse this row.
Users with [**Manage Programs**](https://help.easyagile.com/easy-agile-programs/permissions.md#The%25E2%2580%259CManagePrograms%25E2%2580%259Dpermission)[permission](https://help.easyagile.com/easy-agile-programs/permissions.md#The%25E2%2580%259CManagePrograms%25E2%2580%259Dpermission) will see the "+ Milestone" button at the right-hand end.
### Reordering team boards
Click the "..." button on the right-hand end of any team board swimlane to find the "Move up" and "Move down" options:
The team board order will be saved for your view only; other users may set the team boards in a different order.
The "Shared team features" swimlane will always show at the top of the Program board page.
### Making and changing plans
The Program board *visualizes* plans, but most changes can't be made directly on this page.
[**Team**](https://help.easyagile.com/easy-agile-programs/what-is-a-team-in-easy-agile-programs-configuring-.md)**-level plans** can be adjusted on the [**Team planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md). Click on a team board name to open that page and:
* Create new items.
* Schedule items in sprints or dated columns.
* Create [dependencies](https://help.easyagile.com/easy-agile-programs/dependencies.md#Creatingdependenciesbetweenteam-levelissuesinEasyAgilePrograms) within the team, or with other teams.
Team-level items on the Program board page can be toggled with the "Show team level issues" switch in the Filters menu, so you can see the level of detail that suits you.
[**Roadmap-level plans**](https://help.easyagile.com/easy-agile-programs/schedule-features-epics-into-your-increment.md) can be made on the Edit roadmap page.
* Users with [**Manage Programs**](https://help.easyagile.com/easy-agile-programs/permissions.md#The%25E2%2580%259CManagePrograms%25E2%2580%259Dpermission)[permission](https://help.easyagile.com/easy-agile-programs/permissions.md#The%25E2%2580%259CManagePrograms%25E2%2580%259Dpermission) can find the "[Edit roadmap](https://help.easyagile.com/easy-agile-programs/scheduling-issues-from-the-roadmap-backlog.md)" button in the top right-hand corner of the Program board page.
* Roadmap-level items can be planned in the swimlane for a specific team board, or in the "Shared team features" swimlane at the top of the page.
[**Third-level items**](https://help.easyagile.com/easy-agile-programs/third-level-hierarchy.md) are fetched from Jira based on the dates on the items. When the start and end dates of the item mean it overlaps with the Increment dates, the item will show at the top of the Program board page.
## Tracking risks on the Program board
### Scheduling conflicts
A ⚠️ "Warning" symbol will show on roadmap items when their child items are scheduled *after* the planned end date. This highlights when plans might slip.
Click the roadmap item to see *only* its child items:
You can then correct the scheduling by:
* Changing the dates of the roadmap item; or
* Rescheduling the child items.
Rescheduling items on the Program board page is only available when a scheduling conflict is selected.
You can switch off scheduling conflict warnings in [the Filters menu](https://help.easyagile.com/easy-agile-programs/program-board.md#TheProgramboardpage-TheFiltersmenu).
### Dependencies
[Links between items are visualized as dependency lines](https://help.easyagile.com/easy-agile-programs/dependencies.md).
Show or hide dependency lines based on [health/color](https://help.easyagile.com/easy-agile-programs/understanding-dependency-status-health-and-color.md) from the Dependencies dropdown:
To filter *items* based on their dependencies, use [the Filters menu](https://help.easyagile.com/easy-agile-programs/program-board.md#TheProgramboardpage-TheFiltersmenu).
Dependencies dropdown missing on the Program board page?
In earlier versions (before v7.3.0 on Data Center), dependency health filtering was in the "View settings" menu.
By default, one link type is shown: [the type selected when creating or editing the Program](https://help.easyagile.com/easy-agile-programs/configuring-dependencies-for-a-program.md).
**Switch on additional link types in the Dependencies dropdown**. This will show all link types configured for your Jira site, including custom types.
* *Visualizing additional link types is available on Cloud, and Data Center v7.3.0+.*
[**Done** dependencies](https://help.easyagile.com/easy-agile-programs/understanding-dependency-status-health-and-color.md#Donedependencies) are when one or both of the items are already marked as done in Jira. Done dependencies are switched off by default: enable them with "Show done dependencies" in the Dependencies dropdown.
* *Done dependency filtering is available on Cloud, and Data Center v7.1.0+.*
Use the [**Dependencies map**](https://help.easyagile.com/easy-agile-programs/dependency-map.md) to focus on *only* the planned work that's interdependent.
[*Learn more about visualizing links as dependency lines in Easy Agile Programs*](https://help.easyagile.com/easy-agile-programs/dependencies.md)*.*
## Confidence votes
All users on the Program board page can see and use the Confidence vote tool.
In addition to this Increment-level Confidence Vote, separate voting is available on each [**Team planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md).
[*Learn more about Confidence voting*](https://help.easyagile.com/easy-agile-programs/confidence-voting.md)*.*
Confidence voting is available:
* On Jira Cloud (i.e. Jira sites with "....atlassian.net" in the URL) on all pages of the app
* In Data Center version 6.0.0+; [a Jira Administrator can install the latest version](https://confluence.atlassian.com/upm/updating-apps-273875710.html).
## Filtering the Program board
### The Filters menu
Use Filters to reduce the number of items displayed so you can focus on what's important.
Find the "Filters" button at the top of the page to open the Filters drawer:
Filters you apply are added to the page URL, so you can share a link to show the same filtered set of items with someone else!
* Filter items to show only those that have a [dependency of the given health](https://help.easyagile.com/easy-agile-programs/understanding-dependency-status-health-and-color.md).
* If the [Roadmap issue source](https://help.easyagile.com/easy-agile-programs/configuring-the-roadmap-issue-source.md) uses a dedicated roadmap board, apply Quick filters from that Jira board. Board administrators can configure Quick Filters in [Jira Cloud](https://support.atlassian.com/jira-software-cloud/docs/configure-quick-filters/) or [Jira Data Center](https://confluence.atlassian.com/jirasoftwareserver/configuring-quick-filters-938845301.html).
* Filter based on Status Category (**To Do** / **In Progress** / **Done**).
* Select specific team boards to focus on a smaller group of teams.
* Show or hide team-level items.
* Show or hide scheduling conflict warnings.
The Filters button will show the number of filters currently applied. The number of hidden items will be tracked to the left of the button. Use "Clear filters" to remove all filter conditions at once.
*In earlier versions of the app (before v7.3.0 on Data Center), filtering options were split between "Filters" and "View settings".*
### Using hierarchy
Click a **purple** roadmap item to show only its child items:
* If your roadmap is only epics (or epic-level items), this uses the parent-child relationship in Jira: an epic is the Parent of a Story.
* When the [*Roadmap issue source*](https://help.easyagile.com/easy-agile-programs/configuring-the-roadmap-issue-source.md) "Any issue types from a dedicated board", the link between roadmap and team-level items is configured manually for the Program.
Click a third-level item to see its children from the roadmap *and* its children's children from team boards:
## Navigating from the Program board page
* The "[Edit roadmap](https://help.easyagile.com/easy-agile-programs/scheduling-issues-from-the-roadmap-backlog.md)" button is visible for users with [**Manage Programs**](https://help.easyagile.com/easy-agile-programs/permissions.md#The%25E2%2580%259CManagePrograms%25E2%2580%259Dpermission)[permission](https://help.easyagile.com/easy-agile-programs/permissions.md#The%25E2%2580%259CManagePrograms%25E2%2580%259Dpermission).
* Use the arrows next to the Increment name to jump to the previous or next Increment.
* Open the **Team planning** page by clicking on the team board name.
* A blue "Schedule team issues" button will show next to the team board name if no items on this board are scheduled in this Increment yet. This button will also open the Team planning page.
---
language: "en"
---
# The Program list page
Users with [**Manage Programs** permission](https://help.easyagile.com/easy-agile-programs/permissions.md#The%25E2%2580%259CManagePrograms%25E2%2580%259Dpermission) can see an index of all Programs on the **Program list** page.
* [Create a new Program](https://help.easyagile.com/easy-agile-programs/create-a-program.md) from this page.
* Search for any Program by name.
* Click the the name of a Program to open the **Program roadmap** for that Program.
* Click the name of the current or next Increment to go directly to the **Program board** page for that Increment.
* [Jira Administrators can delete a Program from this page](https://help.easyagile.com/easy-agile-programs/create-a-program.md#CreateandeditaProgram-DeleteaProgram).
To open the Program list page from *outside the app*:
* On Jira Cloud, find the "Programs" option in the Apps menu.
* On Jira Data Center, find "View all Programs" in the Boards dropdown.
*Other users can open the app on the Team planning page for their Jira board.* [*Learn more about navigating Easy Agile Programs*](https://help.easyagile.com/easy-agile-programs/navigate-to-your-program.md)*.*
From any page inside the Easy Agile Programs app, click "Easy Agile Programs" in the top left of the app to return to the Program list:
*For users without Manage Programs permission, this is replaced with a link to this documentation.*
---
language: "en"
---
# The Program roadmap page
The **Program roadmap** page shows the high-level plans for your Program. All the Increments in the Program are shown on a timeline.
The page shows:
* [Roadmap-level plans](https://help.easyagile.com/easy-agile-programs/schedule-features-epics-into-your-increment.md)
* [Milestones](https://help.easyagile.com/easy-agile-programs/milestones.md) on the timeline
* [Dependencies](https://help.easyagile.com/easy-agile-programs/dependencies.md) as lines between items
On this page:
* See historic, current, and future Increments on the timeline.
* Increments are split into sprint columns based on the Increment start date and [sprint configuration](https://help.easyagile.com/easy-agile-programs/create-and-edit-a-program-increment.md#CreateandeditaProgramIncrement-Sprintmanagement).
* See [roadmap-level plans](https://help.easyagile.com/easy-agile-programs/schedule-features-epics-into-your-increment.md) on the timeline.
* *Team-level plans (e.g. story-level items scheduled in sprints) and third-level items are not shown on the Program roadmap page.*
* A swimlane for each [team board](https://help.easyagile.com/easy-agile-programs/what-is-a-team-in-easy-agile-programs-configuring-.md) will be shown only if there are roadmap-level items in that swimlane.
* Visualize links between roadmap-level items as [dependency lines](https://help.easyagile.com/easy-agile-programs/dependencies.md) and filter them by health or link type.
* See [Milestones](https://help.easyagile.com/easy-agile-programs/milestones.md) on the timeline.
Users with [**Manage Programs** permission](https://help.easyagile.com/easy-agile-programs/permissions.md#The%25E2%2580%259CManagePrograms%25E2%2580%259Dpermission) can:
* Open the ["Edit program" menu](https://help.easyagile.com/easy-agile-programs/create-a-program.md#CreateandeditaProgram-EditaProgram).
* [Create a new Increment](https://help.easyagile.com/easy-agile-programs/create-and-edit-a-program-increment.md) with the "+ New increment" button.
* [Edit an existing Increment](https://help.easyagile.com/easy-agile-programs/create-and-edit-a-program-increment.md#CreateandeditaProgramIncrement-EditanIncrement) from the "..." menu in the top right-hand corner of that Increment.
* Create, edit or delete [Milestones](https://help.easyagile.com/easy-agile-programs/milestones.md) by clicking on an existing Milestone or the "+ Milestone" button.
* [Open the **Edit roadmap** page to schedule issues on the roadmap](https://help.easyagile.com/easy-agile-programs/scheduling-issues-from-the-roadmap-backlog.md).
## Navigating from the Program roadmap page
* Click an Increment name or the "View increment" button to open the **Program board** page for that Increment.
* Click a team board name to open that team's **Team planning** page for that Increment.
* The "[Edit roadmap](https://help.easyagile.com/easy-agile-programs/scheduling-issues-from-the-roadmap-backlog.md)" button is visible for users with [**Manage Programs**permission](https://help.easyagile.com/easy-agile-programs/permissions.md#The%25E2%2580%259CManagePrograms%25E2%2580%259Dpermission).
---
language: "en"
---
# Programs app data storage
Easy Agile is committed to Cloud security.
* **Easy Agile's cloud services are** [**SOC 2 Type II certified**](https://trust.easyagile.com/resources)**.**
* Easy Agile Programs is a [Cloud Fortified](https://developer.atlassian.com/platform/marketplace/cloud-fortified-apps-program/) Atlassian Marketplace app.
## Data stored for Easy Agile Programs
Easy Agile Programs uses two types of data: Jira data, and app-specific end-user data.
| | **Jira data** | **App data** |
| **Examples** | Epics and issues Projects, boards, and sprints Issue fields including the Story Points field User names and email addresses | [Program](https://help.easyagile.com/easy-agile-programs/create-a-program.md) and [Increment](https://help.easyagile.com/easy-agile-programs/create-and-edit-a-program-increment.md) configuration [Confidence vote responses](https://help.easyagile.com/easy-agile-programs/confidence-voting.md) [PI Objectives](https://help.easyagile.com/easy-agile-programs/objectives.md) [Milestones](https://help.easyagile.com/easy-agile-programs/milestones.md) [Sprint capacity estimates](https://help.easyagile.com/easy-agile-programs/estimations.md) entered on the [Team planning page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md) |
| **Storage** | Easy Agile apps never store a copy of your Jira data. Jira data is fetched directly from Jira when a user loads the page, using that user's Jira authentication. Where app data is related to Jira data, we store only the ID number of the relevant Jira data (e.g. the board ID number or user hexadecimal ID). | **For Cloud:** data that can't be stored in Atlassian Jira is saved in Easy Agile's cloud servers. Read more about Data residency for Cloud customers below. **On Data Center:** app data is stored in the existing Jira database. The app adds and manages new tables with names starting with "AO_349192_". Easy Agile cannot access your Jira or app data. |
|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
End users can choose to share personal information such as their name and email address with Easy Agile. This includes:
* Entering their details in the [in-app welcome screen](https://help.easyagile.com/easy-agile-teamrhythm/security-privacy.md#How-do-I-disable-the-in-app-%25E2%2580%259CWelcome%25E2%2580%259D-video-and-signup-form?)
* [Contacting our support team](https://help.easyagile.com/easy-agile-teamrhythm/how-to-raise-a-support-request.md)
The Easy Agile Program app processes but does not store this personal information. All PII is stored in services in our [listed subprocessors](https://trust.easyagile.com/subprocessors).
Read more about what kinds of data we collect in our [Privacy Policy](https://www.easyagile.com/trust-center/privacy-policy/), or download our Data Processing Addendum (DPA) from [trust.easyagile.com](http://trust.easyagile.com).
### Data residency for Cloud customers
For our Cloud customers, app data that cannot be stored in Jira is stored in Easy Agile's cloud servers (outside Atlassian).
* The app integrates with Jira through the Atlassian Connect Framework. [This includes using a shared installation secret to manage authentication with Jira](https://developer.atlassian.com/cloud/jira/platform/security-for-connect-apps/#about-the-installation-secret). This secret is stored in our cloud servers in addition to the app data.
* Team member access to production infrastructure is restricted by our Security and IT team and subject to audit logging. Team members who are part of an administrator group, or can request access, are required to use biometric authentication.
Easy Agile's cloud infrastructure is operated from [AWS regions](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html) in the following countries:
1. In the USA: us-west-2 in Oregon
2. In Germany: eu-central-1 in Frankfurt
Which region your app data is assigned to will depend on where the host Jira site is pinned ***at the time Easy Agile Programs is installed***:
* By default, customers will be assigned to the USA region.
* If your Jira site is pinned to Germany at the time of installation, the Easy Agile Programs app data will be assigned to the region in Germany.
* If your Jira site is pinned elsewhere in the EU, Atlassian will determine the nearest supported region to assign your installation
A note on Atlassian's [Data residency for Connect apps](https://developer.atlassian.com/cloud/jira/platform/data-residency/) implementation:
[Customers who don't have a data residency requirement, but are provisioned in a supported region for performance reasons, install into the nearest supported realm](https://developer.atlassian.com/cloud/jira/platform/data-residency/#realm-pinning).
It is not currently possible to manually select or change the data residency region for Easy Agile Programs after the app has been installed.
If you're interested in more data residency region options, [let us know here](https://arijea.atlassian.net/servicedesk/customer/portal/2/group/99/create/302?summary=Re%3A+Programs+data+residency).
### App data after uninstallation
If you uninstall the Easy Agile Programs app from your Jira site:
* App data will no longer be accessible.
* The data will *not* be deleted from the Easy Agile cloud servers or Jira Data Center database where it is stored.
* Jira data (e.g. issues, epics, sprints, versions) that has been viewed or edited using the app will not be affected by uninstallation.
If you re-install the app again in the future, your data will be restored.
* On Jira Data Center, you can safely uninstall/re-install the app to troubleshoot technical issues. No data will be lost and the app will function as normal after re-installation.
## How we keep data safe in our cloud
### SOC 2 Type II
**Easy Agile's cloud services are** [**SOC 2 Type II certified**](https://trust.easyagile.com/resources)**.**
Learn more about Easy Agile's security compliance and controls at [trust.easyagile.com](http://trust.easyagile.com).
[System and Organization Controls](https://www.lbmc.com/services/audit-assurance/soc-audit/) (SOC) 2 is a widely recognized security standard developed by the AICPA that specifies how organizations should manage customer data. This means that we've undergone an audit and assessment to ensure their security controls meet AICPA's Trust Services Criteria, including:
* Security
* Availability
* Processing integrity
* Confidentiality
### Easy Agile Programs is a Cloud Fortified Atlassian Marketplace app
All Easy Agile apps are Cloud Fortified, earning [the highest badge on the Atlassian Marketplace for security and reliability](https://www.atlassian.com/trust/marketplace?source=app-listing-badge&tab=administrative-visibility-and-control#:~:text=Security%20Participant%20apps-,Cloud%20Fortified%20apps,-Privacy).
As a Marketplace Partner, we follow the Atlassian guidelines for security:
* [Security guidelines for Marketplace Partners](https://developer.atlassian.com/platform/marketplace/vendor-security-guidelines/?utm_medium=docs&utm_source=easy-agile-user-story-maps&utm_campaign=security)
* [Atlassian's app vulnerability scanning platform, Ecoscanner](https://developer.atlassian.com/platform/marketplace/ecoscanner/)
* [Marketplace Security Bug Bounty Program](https://developer.atlassian.com/platform/marketplace/marketplace-security-bug-bounty-program/)
* [Vulnerability management for Marketplace apps](https://developer.atlassian.com/platform/marketplace/vulnerability-management-for-marketplace-apps/)
* [App security incident management guidelines](https://developer.atlassian.com/platform/marketplace/app-security-incident-management-guidelines/?utm_medium=docs&utm_source=easy-agile-user-story-maps&utm_campaign=security)
* [Atlassian Cloud App Operations Guide](https://developer.atlassian.com/platform/marketplace/cloud-app-operations-guide/?utm_medium=docs&utm_source=easy-agile-user-story-maps&utm_campaign=security)
Our Jira Cloud apps require the following [Atlassian Connect Permissions (Scopes)](https://developer.atlassian.com/static/connect/docs/latest/scopes/scopes.html): Read, Write, Delete, and Project Administration. Project Administration is needed for creating and updating [Release versions](https://support.atlassian.com/jira-software-cloud/docs/create-a-version-in-a-classic-project/).
---
language: "en"
---
# Easy Agile Programs Cloud / Data Center differences
**Easy Agile Programs is available for Jira Cloud (SaaS) and Jira Data Center (on-premise/self-hosted).** Use the type that matches your host Jira site.
[Easy Agile TeamRhythm data can be migrated to Jira Cloud using JCMA](https://help.easyagile.com/easy-agile-programs/migrating.md).
Jira Server availability
Easy Agile Programs was available for Jira Server prior to [Atlassian's End of Support for Server products](https://www.atlassian.com/blog/announcements/farewell-to-server). The Server and Data Center versions of the app worked identically.
To add the app to a Jira Server site, you'll need to purchase a Data Center license for Easy Agile Programs. [Make sure to check which versions of the app are compatible with your host Jira version](https://marketplace.atlassian.com/apps/1219491/easy-agile-programs-pi-planning-program-board-dependencies/version-history).
The app works the same way on Cloud and Data Center as much as possible. This includes using the same user interface on both Cloud and Data Center.
However, there are some variations due to the differences between Cloud and Data Center technologies.
## Version updates
**On Cloud:** **Most updates are applied automatically** , however, [**some updates require manual approval** from a Jira Site or System Administrator before they can be applied.](https://help.easyagile.com/easy-agile-support/app-updates-maintenance)This happens when the app's permissions or scopes have changed (for example, the app needs access to additional Jira data to support new functionality).
Until the update is approved, your site will continue to run the previous version of the app.
**On Data Center:** Updates to the app are released in [numbered versions](https://marketplace.atlassian.com/apps/1219491/easy-agile-programs-pi-planning-program-board-dependencies/version-history?versionHistoryHosting=dataCenter). [A Jira Administrator will need to manually install updates from the Manage apps page in Jira](https://confluence.atlassian.com/upm/updating-apps-273875710.html).
New functionality is released on Cloud first, and then included in the next Data Center version.
## Data storage
**On Cloud:** Data that can't be stored in Atlassian Jira is saved in Easy Agile's cloud servers. It isn't possible to query the database directly.
**On Data Center:** App data is stored in the existing Jira database. The app adds and manages new tables with names starting with "AO_349192_". Easy Agile cannot access your app data.
[Read more about what data the app stores and how data storage is securely handled](https://help.easyagile.com/easy-agile-programs/programs-app-data-storage.md).
### API access
**On Cloud:** Due to [authentication requirements for Connect apps](https://help.easyagile.com/easy-agile-programs/programs-secure-jira-integration.md#Programs'secureJiraintegration-JiraCloudandAtlassianConnect), we do not support access to the REST API on Cloud.
**On Data Center:** [The app's REST API is accessible to fetch data about Programs, Increments and other app data](https://help.easyagile.com/easy-agile-programs/easy-agile-programs-api.md).
## Functionality
### Issue view
**On Cloud:** Clicking an issue key in the Easy Agile Programs app opens the native Jira issue view. This uses the Issue/Work item screen and layout configured in Jira.
**On Data Center:** It isn't possible to open the native Jira issue view from an app.
Clicking an issue key opens an in-app issue view with a limited range of fields. Open the Jira issue in a new tab to view more.
### Issue hierarchy
**On Cloud:** [Work item (issue) type hierarchy configuration is only available on Jira Cloud Premium or Enterprise](https://support.atlassian.com/jira-cloud-administration/docs/configure-the-issue-type-hierarchy/).
If you have hierarchy configured using Premium or Enterprise:
* [Roadmap configurations that use "epic-level issues"](https://help.easyagile.com/easy-agile-programs/configuring-the-roadmap-issue-source.md#ChoosingtheRoadmapissuesourceforyoursituation) will use all issue types configured at that level.
* You can use the "Parent" link type when [configuring third level hierarchy](https://help.easyagile.com/easy-agile-programs/third-level-hierarchy.md) to use your existing hierarchy from Jira.
**On Data Center:** [Issue type hierarchy configuration is configured with Advanced Roadmaps](https://confluence.atlassian.com/jirasoftwareserver/configure-your-jira-software-instance-1044784156.html#ConfigureyourJiraSoftwareinstanceforAdvancedRoadmaps-CustomHierarchyLevelsARJ). [Advanced Roadmaps is now built into Jira Data Center](https://confluence.atlassian.com/jirasoftwareserver/discover-advanced-roadmaps-for-jira-1044784153.html).
You can use the "Parent" link type when [configuring third level hierarchy](https://help.easyagile.com/easy-agile-programs/third-level-hierarchy.md) to use your existing hierarchy from Jira.
Third level hierarchy can also be configured using Issue links. This method is available on all versions of Jira.
### "Program" and "Program Increment" custom fields
**On Jira Cloud:** The "Program" and "Program Increment" custom fields show the name of that Program or Increment in **plain text**.
**On Data Center:** When viewing an issue in Jira, click the Program or Program Increment to navigate directly to that page in Easy Agile Programs.
## App administration
**On Cloud:** Disabling app modules is not available on Cloud.
[Data security policies](https://support.atlassian.com/security-and-access-policies/docs/manage-data-security-policy-rules/) can be used to [block app access](https://support.atlassian.com/security-and-access-policies/docs/block-app-access/) to Jira projects.
**On Data Center:** [Jira Administrators can disable analytics, crash reporting, and the product intro page](https://help.easyagile.com/easy-agile-programs/security-privacy.md).
---
language: "en"
---
# Programs custom fields
Easy Agile Programs adds two custom fields to Jira: "Program" and "Program Increment". These can be used for reporting.
These fields will be shown on the "View Issue" screen once an issue is scheduled in a Program. Since the fields are read-only, they won't be available on the "Create Issue" screen. Please click [here for instructions on how to add the fields to your screens](https://help.easyagile.com/easy-agile-programs/Programs-Custom-Fields.1933246830.html#ProgramsCustomFields-Addingcustomfieldstoscreens).
## Which issues will custom fields be added to?
Custom fields will only be added to issues on the [**Program roadmap**](https://help.easyagile.com/easy-agile-programs/program-roadmap) and issues scheduled in sprints/columns on the [**Team Planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board).
[Third-level issues](https://help.easyagile.com/easy-agile-programs/third-level-hierarchy) and subtask issue types will **not** have custom fields added to issues.
### Roadmap issues
Roadmap issues will have custom fields added when:
* Issues are drag-and-dropped on the [Increment Roadmap](https://help.easyagile.com/easy-agile-programs/increment-roadmap)
* Issues added to the roadmap with [date syncing](https://help.easyagile.com/easy-agile-programs/date-syncing-with-native-jira-date-fields) when you open the Program or Increment in the app.
**Custom fields on date-synced issues are currently available:**
* on Jira Cloud (i.e. Jira sites with "....atlassian.net" in the URL)
* on Jira Data Center with app version v7.2.0+
### Team issues
Team issues will have custom fields added when they're scheduled:
* Using drag-and-drop on the [**Team Planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board) (Scrum boards and Kanban boards)
* In [sprints in Jira that are synced with an Increment](https://help.easyagile.com/easy-agile-programs/sprints.md)
## Reporting with Program custom fields
### JQL Search
JQL search can be used to identify issues that have been scheduled into a Program and/or Program Increment.
* `"Program Increment" = "Program Increment Name"` to pull a list of all the issues that have been scheduled in that Program Increment
* `"Program" = "Program Name"` to pull a list of all the issues that have been scheduled in that Program
You can also use the custom fields together for more targeted JQL searching, or where there may be multiple Program Increments with the same name i.e Q1 FY20.
* `"Program" = "Program Name" AND "Program Increment "= "Program Increment Name"`
### Integrating with other tools
The Programs custom fields can be used by your reporting tools for tracking and visibility.
If you're using eazyBI, [please refer to our integration guidelines here.](https://help.easyagile.com/easy-agile-programs/eazybi.md)
If you're using an alternative tool and would like a smoother experience [please reach out to us](https://arijea.atlassian.net/servicedesk/customer/portal/2/group/2/create/30).
## Configuring custom fields
### Company-managed and Data Center projects
To see the "Program" and "Program Increment" fields on the issue view in Jira, they'll need to be on the *Issue screen* in Jira.
* These fields are read-only (and can only be edited by the Easy Agile Programs app). They'll never show on the Create or Edit screen in Jira Data Center.
* Only Jira Administrators can edit Jira Issue screen configuration.
An *Issue screen* in Jira controls the fields shown for an issue.
Jira projects use an *Issue screen scheme* to control which *Issue screens* are used on which issue types.
[See how Field configuration works in Jira here](https://confluence.atlassian.com/adminjiraserver/configuring-issues-938847082.html).
To quickly associate a custom field with multiple Issue screens:
1. Open the Jira settings page "Custom fields" in [Jira Cloud](https://support.atlassian.com/jira-cloud-administration/docs/add-a-custom-field-to-a-screen/)or [Jira Data Center](https://confluence.atlassian.com/adminjiraserver/managing-custom-fields-1047552711.html)
2. Search for the field name "Program".
3. Use the "..." button on the right to find the "Associate to Screens" button.
4. Select the Issue screen(s) for each Jira project which will use the fields.
### Team-managed projects (Jira Cloud only)
Project Administrators can add the "Program" and "Program Increment" custom fields to issues in [a team-managed project](https://support.atlassian.com/jira-software-cloud/docs/what-are-team-managed-and-company-managed-projects/).
On [the settings page for an Issue type](https://support.atlassian.com/jira-software-cloud/docs/customize-an-issues-fields-in-team-managed-projects/), search for custom fields to drag and drop them into the issue layout.
## Troubleshooting custom fields
### Why are the Program \& Program Increment custom fields only visible on some of my issues in a Program?
If roadmap issues with dates have missing or outdated custom fields, open the [Program roadmap](https://help.easyagile.com/easy-agile-programs/program-roadmap), [Program board](https://help.easyagile.com/easy-agile-programs/program-board) or [Team planning](https://help.easyagile.com/easy-agile-programs/team-planning-board) page. This will trigger a sync for that Program. Changes may take several minutes to take effect on your Jira issue.
* On earlier versions of the app, custom fields were not added to date-synced roadmap issues. This is available on Data Center v7.2.0 and later, and on Cloud. On Data Center, update the app (or ask a Jira Administrator to) to resolve this.
If a board has been deleted from Jira, remove the board from the Program configuration in the [Edit Program menu](https://help.easyagile.com/easy-agile-programs/create-a-program#CreateandeditaProgram-EditaProgram).
Ensure you have access to all the boards in the Program so that custom fields can be successfully added and removed.
If you're on the latest version and not seeing the custom fields on your Jira issues, a Jira Administrator may need to add the fields to the correct issue screens, as described [above](https://arijea.atlassian.net/wiki/spaces/EAPD/pages/edit-v2/1933246830#Configuring-custom-fields).
### I am using shared sprints across more than one Program and the custom fields aren't working as expected.
We recommend that you don't use the same ['shared sprints'](https://help.easyagile.com/easy-agile-programs/create-and-edit-a-program-increment.md) across Programs as our custom fields will not work as intended. When an issue is put in a sprint that's associated with a Program we set the custom fields "Program" and "Program Increment" on the issue for visibility and reporting. When the same sprints are used across multiple Programs, the custom fields will be added for one Program/Program Increment only.
### Which user will field updates be attributed to?
**On Jira Cloud**, updates to the "Program" and "Program Increment" custom fields are not listed in issue history. The fields will be automatically updated by the app for issues that are included in a Program Increment.
**On Jira Data Center,**updates to the "Program" and "Program Increment" custom fields will be attributed to either:
* A user who made a change in the Easy Agile Programs app (such as scheduling an issue on the [Team planning page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md))
* A user who changed the issue's sprint in Jira where the sprint is [synchronized with an Increment](https://help.easyagile.com/easy-agile-programs/configuring-sprint-sync-for-an-increment.md)
* "Anonymous" when the app synchronized the custom fields in a background job (in app v8.1.0+)
*  In v7.2.0-v8.0.0, background sync updates were attributed to any user who triggered the sync by opening the app. The user's name was used even for updates on issues they were not able to access in Jira.
These custom fields are locked, and can only ever be updated by the app. Updates to these 2 fields made by "Anonymous" are not indicative of unauthorized users.
#### **On Data Center and want to remove "Anonymous" custom field updates?**
In Easy Agile Programs v8.2.1+, you can create a named user to do "Program" and "Program Increment" background sync updates.
If there is a user account with the exact username "Easy-Agile-Programs", the app will use this user for background custom field syncing.
After this user is created, future background updates will be attributed this user instead of "Anonymous".
---
language: "en"
---
# Programs' secure Jira integration
## Is Cloud or Data Center right for me?
Easy Agile Programs is available for both Jira Cloud and for Jira Data Center. Use the version that matches your host Jira site.
While we endeavor to make the app as similar as possible between hosting types, [there are some minor differences in the app between the Data Center and Cloud](https://help.easyagile.com/easy-agile-programs/programs-cloud-data-center-differences.md).
## How does the app interact with Jira data?
Easy Agile Programs uses Jira's REST APIs to interact with your Jira data.
* The app never stores a separate copy of your Jira data.
On page load, requests are made on behalf of the user to fetch data from Jira's API. When users update Jira data in the app, the update is submitted through the API. This keeps your Jira data as the single source of truth.
[Learn more about what Jira data can be used in Easy Agile Programs here](https://help.easyagile.com/easy-agile-programs/jira-integration.md).
The user's existing Jira permissions control what Jira data they can access within the Easy Agile Programs app. A user will only be able to view or edit Jira data where they already have permission to do so in Jira.
[Learn more about User permissions in Easy Agile Programs here](https://help.easyagile.com/easy-agile-programs/permissions.md).
### Authentication on Jira Cloud
[Requests are authenticated using a user's JWT according to the Atlassian Connect framework](https://developer.atlassian.com/cloud/jira/platform/understanding-jwt-for-connect-apps/). This JWT, including its expiration time, is provided and managed by Atlassian.
## Jira Cloud and Atlassian Connect
The app integrates with Jira Cloud through the [Atlassian Connect Framework](https://developer.atlassian.com/cloud/jira/platform/security-for-connect-apps/). This facilitates the authentication process for interacting with your Jira site, including:
* Using [JWT (JSON Web Tokens)](https://developer.atlassian.com/cloud/jira/platform/understanding-jwt-for-connect-apps/) to access protected resources such as Jira's REST APIs
* Using Jira's existing permissions models to manage what Jira data a user can view, edit, or delete
App-specific data that cannot be stored as Jira data is stored in Easy Agile's cloud servers. This is also authenticated using the [installation secret for the Connect app](https://developer.atlassian.com/cloud/jira/platform/security-for-connect-apps/#about-the-installation-secret).
* Learn more about [what app data is stored for Easy Agile Programs here](https://help.easyagile.com/easy-agile-programs/programs-app-data-storage.md).
Easy Agile Programs does not currently use Atlassian's [Forge](https://developer.atlassian.com/platform/forge/) platform. We are following [Atlassian's progress on feature parity with Atlassian Connect](https://ecosystem.atlassian.net/jira/polaris/projects/ROADMAP/ideas/view/5848894) to plan the right time to migrate to Forge.
### Scopes
Our Jira Cloud apps require the following [Atlassian Connect Scopes (Permissions)](https://developer.atlassian.com/cloud/jira/platform/scopes-for-connect-apps/):
* `READ`, `WRITE`, `DELETE` to fulfil user actions to update Jira data
* `PROJECT_ADMIN` may be used for visualizing [Release versions](https://support.atlassian.com/jira-software-cloud/docs/create-a-version-in-a-classic-project/)
---
language: "en"
---
# Purchasing & Administration
You can purchase Easy Agile Programs on the Atlassian Marketplace.
[Find Easy Agile Programs on the Atlassian Marketplace here](https://marketplace.atlassian.com/apps/1219491/easy-agile-programs-pi-planning-program-board-dependencies).
All [Easy Agile apps](https://www.easyagile.com/products/) are sold through the [Atlassian Marketplace](https://marketplace.atlassian.com/vendors/1212045/easy-agile). Please see the following guides for:
* [Easy Agile app trials / evaluations](https://help.easyagile.com/easy-agile-support/app-trials-evaluations.md)
* [Easy Agile app licensing and pricing](https://help.easyagile.com/easy-agile-support/app-licensing-and-pricing.md)
## Guides to app administration
* [Easy Agile Programs installation](https://help.easyagile.com/easy-agile-programs/trial-installation.md)
* [Permissions for Easy Agile Programs](https://help.easyagile.com/easy-agile-programs/permissions.md)
* [Security \& Privacy](https://help.easyagile.com/easy-agile-programs/security-privacy.md)
* [Compatibility \& Performance](https://help.easyagile.com/easy-agile-programs/compatibility-performance.md)
* [Migrating Easy Agile Programs](https://help.easyagile.com/easy-agile-programs/migrating-easy-agile-programs.md)
* [Requesting a usage overview for Easy Agile Programs](https://help.easyagile.com/easy-agile-programs/requesting-a-usage-overview-for-easy-agile-programs.md)
---
language: "en"
---
# Reports
Easy Agile Programs provides in-app reports pages for:
* Dependencies
* Objectives
* Delivery Insights
## Dependencies report
The Dependencies report provides summarized information about the dependencies in an Increment. This helps you identify which dependencies could be a risk so that you can anticipate problems before they happen. [Learn more about Dependencies reports here.](https://help.easyagile.com/easy-agile-programs/dependencies-reports.md)
## Objectives report
Use the Objectives report to see and track all the [Team PI Objectives](https://help.easyagile.com/easy-agile-programs/objectives.md) in an Increment. [Learn more about the Objectives report here](https://help.easyagile.com/easy-agile-programs/objectives-report.md).
## Delivery Insights
Delivery Insights helps you understand if your program is on track by surfacing patterns across multiple teams. You get a consolidated view of cycle time, throughput, and work in progress with AI-generated observations, impact and recommendations.
Delivery Insights is available on Jira Cloud only.
## Dependency map
For a focused view of dependencies in an Increment, try the [Dependency map](https://help.easyagile.com/easy-agile-programs/dependency-map.md).
## Custom reporting with JQL
Easy Agile Programs adds the "Program" and "Program Increment" custom fields to scheduled Jira issues. This allows you to use your existing dashboards and tools for reporting based on these fields.
See [Reporting with Program custom fields](https://help.easyagile.com/easy-agile-programs/programs-custom-fields#ProgramsCustomFields-ReportingwithProgramcustomfields) for more details.
## eazyBI integration
eazyBI can be configured to detect the "Program" and "Program Increment" custom fields. This enables you to build reports based on these fields when using your Jira issues in eazyBI.
[See this page for more information on using Easy Agile Programs and eazyBI](https://help.easyagile.com/easy-agile-programs/eazybi.md).
---
language: "en"
---
# Requesting a usage overview for Easy Agile Programs
If you need to know how many people are actively using Easy Agile Programs, our support team can prepare a usage overview for your Jira site.
There's no in-product usage report, so requesting an overview from support is the way to get these numbers.
## What a usage overview includes
Depending on what you need, your overview can cover:
* Unique active users per month and trends over a period of time
* How many teams (boards) are actively using Easy Agile Programs and a list of board IDs
* Activity for each Program, including the number of unique users and which months each Program was active
* Usage information for key product features
* Peer benchmarking so you can see how your utilisation compares with other similar-sized customers
* Insights to help identify where enablement could improve usage
Tell us what you're trying to answer and we can help to tailor the report for your needs.
## What we can't provide
So you know what to expect before you ask:
* **User details:** For privacy reasons we don't capture user information.
* **Program owner, creator or last updated date:** We can tell you how many people used a Program and how often, but not who created it or who changed it last.
* **Program names:** We can provide Program IDs, which are our internal identifiers and won't match the names your teams use.
* **Board or project names:** We don't capture the names of boards or projects. We can give you the board IDs, and you can cross-reference them to projects and teams in your Jira site.
* **Groupings by department:** We can't split usage by your internal organisational structure.
* **Scheduled or recurring reports:** There's no automated way for us to send this data on a monthly or annual schedule. You're welcome to request a fresh overview whenever you need one.
* **Usage information if analytics have been turned off:** [Product analytics need to be enabled](https://help.easyagile.com/easy-agile-programs/security-privacy.md#Analytics) on your instance for us to have usage data. If we can't see any activity for your site, get in touch and we'll talk through the alternatives.
## How to request a usage overview
1. Go to the [Easy Agile support portal](https://arijea.atlassian.net/servicedesk/customer/portal/2/group/97/create/233).
2. Let us know which app you need the overview for, and include your licence key or SEN.
3. Tell us what you're trying to answer. For example whether you're preparing a renewal case, auditing your apps, or planning a migration - along with the time period you need.
4. If you have a deadline, mention it and we'll work to it.
We'll come back to you within one to two business days.
### Related pages
* [Easy Agile licensing and pricing](https://help.easyagile.com/easy-agile-support/app-licensing-and-pricing.md)
* [Migrating Easy Agile Programs](https://help.easyagile.com/easy-agile-programs/migrating-easy-agile-programs.md)
* [Contact the Easy Agile support team](https://help.easyagile.com/easy-agile-programs/help-support.md)
---
language: "en"
---
# Planning on the Increment roadmap
## Editing the roadmap
There are 2 ways to schedule issues onto the Roadmap for your Program Increment:
1. Using [drag and drop on the Edit Roadmap page](https://help.easyagile.com/easy-agile-programs/scheduling-issues-from-the-roadmap-backlog.md).
2. Configuring [date syncing](https://help.easyagile.com/easy-agile-programs/date-syncing-with-native-jira-date-fields.md) to automatically populate the Roadmap based on date fields in Jira.
## How are roadmap issues used?
Roadmap issues will be shown on:
|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| The [**Program roadmap**](https://help.easyagile.com/easy-agile-programs/program-roadmap.md) shows all roadmap issues scheduled across Increments. |  |
| The [**Program board**](https://help.easyagile.com/easy-agile-programs/program-board.md) shows roadmap issues in the "Shared Team Features" swimlane at the top and in each team swimlane * Roadmap issues will be shown in **purple**. * Team-level issues (if enabled in "View settings" dropdown) are shown in white issue cards. |   |
| The [**Team planning** page](https://help.easyagile.com/easy-agile-programs/team-planning-board.md) shows only the roadmap issues from: * That team's swimlane * The "Shared Team Features" swimlane |  |
*** ** * ** ***
## FAQs
### Can I add other issue types to the Roadmap (other than Epics)?
Yes, you can add issue types other than Epics onto the Roadmap. When [creating a Program](https://help.easyagile.com/easy-agile-programs/create-a-program.md), under the *Roadmap Board* section, select the third option '*I want to schedule other issue types from a dedicated board onto my Program Roadmap' (*the first 2 options are strictly for scheduling Epics onto the Roadmap).
.png?cb=d5ad6bc89b423b009d36ac4b32dfc63b)
Once you have selected this option, under the *Roadmap Board* section, you need to select the Board where the issues you want to schedule onto your Roadmap live.
Finally, you must choose the Jira issue link type that connects your Roadmap issues to the issues scheduled in the team Sprints.
### Order of features on the Edit Roadmap screen doesn't match the Program Board
Programs enables you to order features on the **Edit Roadmap** screen so you can prioritize upcoming work. This order will also be reflected on the [Program board](https://help.easyagile.com/easy-agile-programs/program-board.md) if Jira's issue ranking is enabled on the board(s).
If the order of your features on the Edit Roadmap screen is *not* reflected in the Program Board, first check the board configuration to enable issue ranking.
To confirm issue ranking is enabled on your board, make sure the board filter query includes the following clause:
ORDER BY Rank ASC
See [Enable ranking in the Jira help documentation](https://support.atlassian.com/jira-software-cloud/docs/enable-ranking/) for more information.
---
language: "en"
---
# Scheduling issues from the Roadmap backlog
On the *Edit roadmap* page, you can schedule issues onto your roadmap. This might be Jira epics, features, or other Jira issues used to represent your big-picture plans.
Only users with [**Manage Programs** permission](https://help.easyagile.com/easy-agile-programs/permissions.md#The%25E2%2580%259CManagePrograms%25E2%2580%259Dpermission) can access the Edit roadmap page.
Open the *Edit roadmap* page from the [**Program roadmap**](https://help.easyagile.com/easy-agile-programs/program-roadmap.md) or [**Program board**](https://help.easyagile.com/easy-agile-programs/program-board.md)**page**:
To plan your roadmap on this page:
* Schedule issues with drag-and-drop.
* Resize issues by dragging the start or end of the feature on the roadmap.
* Schedule issues into the "Shared team features" swimlane to show issues on the [Team Planning](https://help.easyagile.com/easy-agile-programs/team-planning-board.md) page for all teams.
If you have [date syncing](https://help.easyagile.com/easy-agile-programs/date-syncing-with-native-jira-date-fields.md) enabled, editing issues on this screen will update the date fields on that issue in Jira.
*** ** * ** ***
## What issues are in the Roadmap Backlog?
The issues on your roadmap backlog in Easy Agile Programs are based on [your Program configuration](https://help.easyagile.com/easy-agile-programs/create-a-program.md).
The *roadmap issue source* will be one of these 3 options:
| **"Jira epics from my team boards"** | The issues in the backlog will be Jira epics from the team boards added to your program. You will find each of these team boards listed in the dialog. |  |
| **"Jira epics from a dedicated board"** | The issues in the backlog will be Jira epics from a dedicated agile board |  |
| **"Any issue types from a dedicated board"** | The issues in the backlog will be any issue type from a dedicated agile board |  |
|----------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
### Issues missing from the Roadmap Backlog?
Issues might be missing from the Roadmap Backlog if:
* The issues are Done (ie. in the "Done" Status Category in Jira).
* They're not in the *Roadmap issue source* configured for the Program.
* Check that the issues appear on the board in Jira that you've selected as a team/roadmap board. The *Board filter query* may need to be updated!
* [Learn more about Jira boards and Easy Agile Programs](https://help.easyagile.com/easy-agile-programs/what-is-a-team-in-easy-agile-programs-configuring-.md#Learning-more-about-boards)
* They're already scheduled in this Increment.
* If you're using issue types other than Epics, the issues might be scheduled at a team level.
* If you're using the search function, you'll need to use the full issue key (eg. "ABC-123"), not just the number (eg. "123").
* The Jira board configured as the *Roadmap issue source* has been deleted, or you don't have access to it.
**Jira permissions can limit what issues you see in Easy Agile Programs.** If you can't access an issue, project or board in Jira, then you won't be able to see it in the app. A Jira Administrator (or your internal IT support team) can grant you the permissions you need.
**In Jira Cloud only:** If one or more *whole Jira projects* are missing from Easy Agile Programs, but you *can* access those projects in Jira, the project might be blocked from the app.
An Organization admin can configure this for Jira projects by adding a [*Data security policy*](https://support.atlassian.com/security-and-access-policies/docs/what-is-a-data-security-policy/) with an [*App access*](https://support.atlassian.com/security-and-access-policies/docs/block-app-access/)*Policy rule*.
If a project you need in Easy Agile Programs is blocked, you'll need to contact your Jira Administrator or internal IT support team to resolve this.
*** ** * ** ***
## FAQs
### How can I add Quick Filters to this screen?
Quick Filters are available on the Increment Roadmap only when the [Program is configured to use a dedicated roadmap board.](https://help.easyagile.com/easy-agile-programs/create-a-program.md)
These Quick Filters are pulled from your dedicated roadmap board and will need to be created and edited on your Jira Board. For more information on Quick Filters, see Atlassian's documentation on Quick Filters for [Jira Cloud](https://support.atlassian.com/jira-software-cloud/docs/configure-quick-filters/) or [Jira Data Center](https://confluence.atlassian.com/jirasoftwareserver/configuring-quick-filters-938845301.html).
### Can I schedule an issue in multiple increments?
Yes. You can schedule issues into multiple increments. Issues are shown in the Roadmap Backlog and will be available for scheduling into an Increment as long as the issue hasn't been set to "Done".
When an issue is scheduled in multiple increments you will see all increments listed in the Program Increment custom field on the Jira ticket.
### Can I schedule an issue into multiple teams?
Yes. Drag and drop the issue into the 'Shared Team Features' swimlane when the issue will be worked on by more than one team. Issues added to this swimlane will show up on the team planning board for every team in your Program.
[Next Page](https://help.easyagile.com/llms-full.txt/1)