3 Plan Your Project

After creating a project and adding team members, the next step is usually to plan your project. Planning includes such tasks as setting up environments, creating issues to track your work, and defining Agile boards and sprints to manage your team's progress.

These are the Oracle Visual Builder Studio pages you can use to plan your project:

Use this page ... To:

Environments Environments

Add and manage projects' environments and their service instances.

Issues Issues

Create and track issues.

Boards Boards

Manage issues using Agile boards.

Manage Software Development Environments

An environment lets you define and manage Oracle Cloud PaaS, and Oracle Cloud SaaS service instances as a single entity.

You might create an environment for your QA team with an Oracle Database Cloud Service instance to host data, say, and maybe an Oracle Java Cloud Service instance to deploy the application to and run Selenium tests. You could then create a Stage environment that uses the same Oracle Database Cloud Service instance as the QA environment, but a different Oracle Java Cloud Service instance to deploy the application to.

If you're working with Oracle Cloud Applications application extensions, you'll have a VB Studio Development environment that points to your Oracle Cloud Applications development instance (this environment is created automatically if the Application Extension template was used to create the project). You can create additional environments for Oracle Cloud Applications and add the production instance of your current identity domain, or an external Oracle Cloud Applications instance from another identity domain. Note that you can only add one Oracle Cloud Applications instance to an environment. See Add an Oracle Cloud Application's Instance to an Environment in Administering Visual Builder Studio for more information.

If you're working with visual applications, you'll have a VB Studio Development environment that points to your Visual Builder development instance (this environment is created automatically if the Visual Application template was used to create the project). You can create additional environments for visual apps and add the production instance of your current identity domain, or an external Visual Builder instance from another identity domain. Note that you can add only one Visual Builder instance to an environment. See Add a Visual Builder Instance to an Environment in Administering Visual Builder Studio for more information.

You can access and manage the project’s environments from the Environments page:

From the Environments page, you can:

  • Create and delete environments
  • Add or remove service instances from existing environments
  • Update the details of the environment

    The Details tab displays details, such as name and description, for the selected environment. You can also instantly see the health of all service instances comprising each environment right on the Project Home page or on the Environments page.

  • View the details of its service instances

    The Service Instance tab captures information, such as the health status of service instances, their account names, and service IDs, for each environment in a single place, so you won’t have to hunt for it later.

  • View deployments

    The Deployments tab shows deployments for app extensions and visual apps. Use the Application Extensions toggle to show deployments for all projects associated with this environment or use the Visual Applications toggle to show deployments for the current project only.

Set Up an Environment

You can create an environment and add service instances to it from different identity domains. For example, you can add an Oracle Database Cloud Service instance from one identity domain and an Oracle Java Cloud Service instance from another identity domain.

Note:

When a 19.3.2 production instance is upgraded to 19.4.3, all existing service instances across all service types (JCS, ACCS, Visual Builder, Integration Cloud, Content Experience, Mobile and Database) will be removed from the Environment definitions. Existing tagged instances couldn't be migrated to the service instance references in this release. You'll need to manually reselect and add your service instances to your existing environment definitions. The environment definitions still exist after the upgrade, but the service instance references will disappear.

To add or remove a PSM-based service instance, you need credentials of a user who is assigned the administrator role for the service type. To assign or modify roles, see Modifying Identity Cloud Service User Roles in Managing and Monitoring Oracle Cloud.
  1. In the navigation menu, click Environments Environments.
  2. Click Create (or Create Environment if the page is empty).
  3. In Environment Name, enter a unique name. In Description, enter a description.
  4. Click Create.
  5. In the Service Instances tab, click Add.
  6. In the Add Service Instances dialog box, use the toggle to select the type of service instance (Visual Builder, Oracle Cloud Applications, or Infrastructure Services), then select the check boxes of service instances and click Add.

    By default, the dialog box shows the service instances that you can access from the current identity domain.

    If you have a PSM entitlement, you'll see both service instances and IDCS resources in this list. In the Type column, the current identity domain's service instances are marked as IDCS Resource and PSM instances are marked as Visual Builder or Integration (if you're an Oracle Integration user). Selecting a service instance is slightly preferable, since it gives you not only a cleaner URL, but also indicates status and provides access to actions like starting and stopping instances, and more.

    To search for services from another identity domain or account, click Edit and enter the details in the popup that opens.

    To search for a service in another identity domain, enter the identity domain ID and region in the Visual Builder and Infrastructure services tab. You can't change the identity domain for Oracle Cloud Applications. You can only see the list of Oracle Cloud Applications from the current identity domain.

    To add a standalone Visual Builder instance or a Visual Builder instance that's part of Oracle Integration in another identity domain to an environment, you'll need one of these:

    • The instance's identity domain ID, region, and a user's credentials who can access the instance
    • A user's personal access token who can access the instance
    • The Visual Builder instance's base URL and a user's credentials who can access the instance

    See Add the Visual Builder Instance to an Environment.

    To add an Oracle Cloud Applications instance to an environment, you'll need one of these:

    • A user's personal access token who can access the instance
    • Base Oracle Cloud Application's URL and a user's credentials who can access the instance

    See Add an Oracle Cloud Application's Instance to an Environment.

  7. If necessary, repeat steps 5 and 6 to find and add additional service instances from different identity domains and data centers.

Manage an Environment

After creating an environment, you can add and manage its instances, as shown here:

Action How To

Edit an environment's name and description

In the Details tab, click Edit. Edit the details and click Save.

Add a new service instance to an environment In the Service Instances tab, click Add. In the Add Service Instances dialog box, use the toggle to select the type of service instance (Visual Builder, Oracle Cloud Applications, or Infrastructure Services), then select the check boxes of service instances and click Add.

By default, the dialog box shows the service instances that you can access from the current identity domain.

If you have a PSM entitlement, you'll see both service instances and IDCS resources in this list. In the Type column, the current identity domain's service instances are marked as IDCS Resource and PSM instances are marked as Visual Builder or Integration (if you're an Oracle Integration user). Selecting a service instance is slightly preferable, since it gives you not only a cleaner URL, but also indicates status and provides access to actions like starting and stopping instances, and more.

To search for services from another identity domain or account, click Edit and enter the details in the popup that opens.

To search for a service in another identity domain, enter the identity domain ID and region in the Visual Builder and Infrastructure services tab. You can't change the identity domain for Oracle Cloud Applications. You can only see the list of Oracle Cloud Applications from the current identity domain.

To add a standalone Visual Builder instance or a Visual Builder instance that's part of Oracle Integration in another identity domain to an environment, you'll need one of these:

  • The instance's identity domain ID, region, and a user's credentials who can access the instance
  • A user's personal access token who can access the instance
  • The Visual Builder instance's base URL and a user's credentials who can access the instance

See Add the Visual Builder Instance to an Environment.

To add an Oracle Cloud Applications instance to an environment, you'll need one of these:

  • A user's personal access token who can access the instance
  • Base Oracle Cloud Application's URL and a user's credentials who can access the instance

See Add an Oracle Cloud Application's Instance to an Environment.

Start, stop, or restart an instance

In the Service Instances tab, mouse-over the service instance, click Action the Action Menu icon, and select Start, Stop, or Restart.

To check the status of the service, select Refresh Status from the Action the Action Menu icon menu.

Remove a service instance from an environment

In the Service Instances tab, mouse-over the service instance, click Action the Action Menu icon, and select Remove.

Note:

An instance can't be removed if it's associated with any workspace. If you try, an error message displays, listing the impacted users and the number of workspaces they have. You'll be instructed to ask those users to delete their workspaces. Once this has been done, you can go back and retry the Remove operation.

Delete an environment

In the environments list, mouse-over the environment, click Action the Action Menu icon, and select Delete.

Remember that service instances of the environment aren’t deleted.

Note:

An environment can't be deleted if it's associated with any workspace. If you try, an error message displays, listing the impacted users and the number of workspaces they have. You'll be instructed to ask those users to delete their workspaces. Once this is done, you can go back and retry the Delete operation.

Track and Manage Tasks, Defects, and Features

Use issues to track new feature requests or enhancements, assign tasks to team members, or file bugs.

You can create, update, and search issues from the Issues page or from Agile boards. You can also use REST APIs to create, retrieve, and update issues.

In a project, you can create an issue as a Task, Defect, or a Feature. If your team uses an Agile Scrum board to update issues, Epic and Story types of issues are also available. An Epic is a larger issue typically composed of multiple smaller sub-issues or Story issues. An Epic must have sub-issues and can span multiple sprints.

These are the key steps you’ll perform to create and track issues:

  1. As the project owner, start by setting up products, components, and releases for your project, which you'll need when you start identifying tasks, defects, and features.

    If the default set of issue fields don’t meet your requirements, create custom fields.

  2. Create issues and assign them to your team members.

  3. Update issues, either from the Issues page or from an Agile board.

Issue Types

An issue can be categorized into task (or action), defect (or bug), and feature (or enhancement).

You can create these types of issues:

Issue Type Description

Task Task

Indicates a task, which means an action is required.

A Task type issue could be an action such as a piece of work that must be completed within a certain time, or a simple function to be performed.

Defect Defect

Indicates a defect, which means a bug or a fault in the product. This is the default issue type.

A Defect type issue could be an error or a flaw that prevents the software from working correctly, or creates an unexpected output.

Feature Feature

Indicates a new feature or an enhancement request.

A Feature type issue could be a request to add a new aspect or characteristic to the product, or enhance an existing feature.

Epic Epic

Indicates an Epic, a unit of work that cannot be completed in one sprint. It can contain any other types of sub-issues necessary to complete that work.

An Epic is a larger issue, typically with multiple smaller sub-issues or stories. An epic can span multiple sprints and must have sub-issues (as stories or other issues).

Story Story

Indicates a Story, a sub-issue of a parent epic issue.

The story issues of an epic issue can be allotted to different sprints in an Agile board.

Set Up Issue Products and Custom Fields

Before creating and assigning issues to project members, you can define products, components, default owners of components, and releases for your project. You can create multiple product categories, components, and sub-components; customize the releases; and add custom fields for your project.

You must be a Project Owner to add and manage issue products, components, and custom issues.

Create and Configure Issue Products

When you define a product, you also define its releases and components. A product is a category that represents an entity. A component is a product subsection. A release is a release name or product number.

You can create multiple products for a project and select them from the Products drop-down list on the create or edit issue page. Each product must have at least one component and one release. For example, you can create a Report product with 1.0, 2.0, 3.0, and PS1 as its releases, and Sales, Marketing, and Demographics as its components.

You can define products, components, and releases from the Administration: Issue Tracking page's Products tab.

Open the Issue Tracking page's Products tab:
  1. In the navigation menu, click Project Administration Gear.
  2. Click Issue Tracking.
  3. Click the Products tab.

Here's a list of the product management tasks you can do from the Product's tab:

Action How To

Create a product

  1. Click + New Product.

  2. On the Create Product page, in Name, specify a unique product name.

  3. To create a release, click + New Release, and enter a release name.

    To make a release the product's default release, click Mark as Default the check mark icon.

  4. To create a component, click + New Component, enter a component name, and select its default owner (optional).

    To make a component the product's default component, click Mark as Default the check mark icon.

  5. To create a Found In tag, click + New Found In Tag, and enter a tag name.

  6. Click Done.

To reorder a release or component, mouse over the name and drag-and-drop it to move it up or down in the list.

View or edit a product

From the products list, select the product. On the right side of the page, view or edit its details.

Delete a product

You can’t delete a product if any issues or merge requests refer to it. First, remove all issues and merge requests that refer to the product, and then remove the product.

  1. In the products list, click Delete the delete icon.

  2. In the Delete Product dialog box, click Yes to confirm.

Create and Configure Custom Fields in an Issue

If an issue's default fields don’t meet your needs, you can create custom fields for your project's issues. You can create and manage the fields from the Issue Tracking page's Custom Fields tab. When you create or update an issue, you can see the custom fields in the New or Edit Issue page's Details section.

  1. In the navigation menu, click Project Administration Gear.
  2. Click Issue Tracking.
  3. Click the Custom Fields tab.

You can create these kinds of custom fields:

  • Single line input text
  • Single selection
  • Multi selection
  • Long text input
  • Time and Date
  • Check box

Here's how to manage custom fields:

Action How To

Create a custom field

  1. Click + New Custom Field.

  2. On the Create Custom Field page, in Name, specify a unique name.

  3. In Label, enter the field's display label.

  4. If you don’t want the custom field to appear as a parameter when new issues are created, deselect the available for New Issues check box.

  5. From the Type drop-down list, select the field type.

    If you select Single Selection or Multi Selection, click + New Value to specify the field’s options.

  6. Click Done.

View or edit a custom field

From the custom fields list, select the field. View or edit its details, located on the right side of the page.

You can’t change a custom field's Name or Type. To edit the value of Name or Type, remove and then recreate the custom field.

Hide a custom field

From the custom fields list, select the field. Select the Obsolete (hidden) check box, located on the right side of the page.

Delete a custom field

  1. In the custom fields list, click Delete the delete icon located to the right of the field name.

  2. In the Delete Custom Field dialog box, click Yes to confirm.

All existing issues will be automatically updated to remove the custom field.

Create Issues

You can create an issue from the Issues page or from the REST API. When you create an issue, it gets assigned a unique ID and is added to the issues list on the Issues page.

When you create an issue, you specify its summary, type, severity and priority, due date, tags, and release. You can assign the issue to a team member or to yourself, or leave the field blank to assign the issue later to a team member.

Create an Issue from the Issues Page
  1. In the navigation menu, click Issues Issues.
  2. Click New Issue.
  3. On the New Issue page, in Summary and Description, enter the issue’s title and description.
  4. In Details, specify the issue type, its severity and priority, product details, release, ownership, and project tags.
  5. In Time, specify the due date and estimate (in days).
    One day is estimated of 8 hours. To specify 3 hours, enter 0.375. To specify 2 days and 2 hours, enter 2.250.
  6. In Agile, specify the effort estimate in Agile story points.
  7. If there are any custom fields defined in your project, fill in the details, as required.
  8. Click Create Issue.

Search Issues

You can search for issues using the pre-defined filters under Standard Searches, My Searches, Shared Searches, or Global Searches. If you can’t find the issue, you can run a basic search or an advanced one.

To run a basic search, use the Search Issues box in the upper-right corner of the Issues page. You can search for a term in the summary, description, or comments of issues. To clear the search term, click Clear Filter the Clear Filter icon.

To run an advanced search, use the Advanced Searches link. You can search for issues using various parameters such as sprints, product, version, date, owner, type, and priority.

To save the search query as a filter, click Save this search. To see the search query expression, click Show Search String. Later, if you want to edit the search query, click Edit this search.

Save a Custom Search

You can save basic or advanced search queries as a custom search filters that can be used later:

  1. On the Issues page, run a basic or an advanced search.
  2. On the search results page, click Save this search.
  3. In the Save Search dialog box, enter the search name.

    The custom search filter is available to you only. To share the search filter with project members, in the Save Search dialog box, select the Shared check box. In Share with the following users, select the users with whom you want to share the search query.

    To share the search filter with all project members, select the Share with everyone check box.

  4. Click OK.
The location where the query filters can be found is determined by the way you configured the search:
  • If you didn’t select the Shared check box, the search query appears as a filter under My Searches.
  • If you selected the Shared check box, the search query appears as a filter under Shared Searches.
  • If you selected the Share with everyone check box, the search query appears as a filter under Global Searches.

To edit a custom search query, mouse over the query under My Searches and click Edit the Edit icon.

To delete a custom search query, mouse over the query under My Searches and click Delete the Delete icon.

Share Custom Search Filters

You can share your existing custom search filters with other project members, which they can use to view the issues as you want:

Element Description

Share a search filter with specific project members

  1. In My Searches, mouse over the filter link, and click Share the Share icon.

  2. In the Start Sharing Search dialog box, select the project member names in Share with following users.

  3. Click OK.

The filter link moves from My Searches to Shared Searches.

Share a search filter with all project members

  1. In My Searches, mouse over the filter link, and click Share the Share icon.

  2. In the Start Sharing Search dialog box, select the Share with Everyone check box.

  3. Click OK.

The filter link moves from My Searches to Global Searches.

Stop sharing a search filter

  1. In Global Searches or Shared Searches, mouse over the filter link and click Stop Share the Stop Sharing icon.

  2. In the Stop Sharing Search dialog box, click OK.

    If the search query is being used by other project members, the dialog box shows their list.

When you stop sharing a search query, it is removed from the Shared Searches or Global Searches list for all project users.

View and Update Issues

To view or update an issue, click the issue’s summary or the ID link on the Issues page. An issue link could also be found in the recent activities feed, wikis, Agile boards, and merge requests.

While updating an issue, you can change its status, properties, reassign it to another member, and change its priority or severity. You can also add comments in the Comments tab, upload attachments in the Attachments tab, and check the update history of an issue in the History tab. Updates made to issues can also be tracked in the recent activities feed of the Project Home page.

Resolve an Issue

You can resolve an issue as Fixed, Invalid, Duplicate, Will not fix, Works for me, or Need info:

  1. Click the issue link to open it in the Issues page.
  2. From the Status drop-down list, select Resolved.
  3. From the Resolution drop-down list, select the resolution.
    Sub-status Indicates ...

    Fixed

    The issue has been fixed and is awaiting feedback from the QA team.

    After verifying the fix, the QA team sets the issue’s status to Verified or Closed.

    Invalid

    The issue isn’t a valid issue.

    Will not fix

    The issue won’t be fixed.

    Duplicate

    The issue is a duplicate of an existing issue.

    Enter the issue ID of the existing issue in Duplicate Of.

    Works for me

    The issue cannot be reproduced.

    Need info

    The current issue description isn't sufficient to reproduce the issue; more information is required.

Mark an Issue as Duplicate

If find a duplicate issue, mark it as a duplicate and specify the original issue:

  1. Click the issue link to open it in the Issues page.
  2. From the Status drop-down list, select Resolved.
  3. From the Resolution drop-down list, select Duplicate.
  4. In Duplicate Of, enter the original issue ID or the summary text, and select the original issue.
  5. Click Save.
Update Time Spent on an Issue

When you work on an issue, create a time spent entry each time you update the issue:

  1. Click the issue link to open it in the Issues page.
  2. In the Time section, click Add Time Spent.
  3. In the Add Time Spent dialog box, in Time Spent, specify the number of days you’ve spent on the issue.
  4. To subtract the value specified in Time Spent from the existing value of Remaining (if set), use the default Reduce remaining ... days by entered Time Spent option.

    If Remaining isn’t set, then the value specified in Time Spent is subtracted from Estimate. The option is disabled if the Estimated field isn’t set.

    To specify the remaining days manually, select the Set to option and specify the remaining estimate.

  5. In Comment, add a comment.
  6. Click OK.
The Time Spent Log section shows the time spent entry of the time spent and updates the graph.
  • To edit the time spent entry, click Edit the Edit Time Spent icon and update the fields in the Edit Time Spent dialog.

  • To remove a time spent entry, click Remove the Remove Time Spent icon and update the fields in the Update Time Spent dialog box.

The remaining time is adjusted automatically.

Associate an Issue with a Sprint

You can associate an issue with a sprint from the Edit Issue page:

  1. Click the issue link to open it in the Issues page.
  2. In the Agile section, from the Sprint drop-down list, click the search box, and select the sprint from the list.
  3. Click Save.
Note that you can associate only one sprint with an issue.
Create a Relationship Between Issues

You can create a parent-child relationship between issues:

Action How To

Create a child issue to an issue

You can create multiple child issues to an issue:

  1. Click the issue link to open it in the Issues page.

  2. Click + New Sub-issue.

  3. Enter details for the new issue and click Create Issue.

  4. In the header, click the parent issue ID to open the parent issue. In the Associations section, verify the child issue ID.

Add a parent issue to an issue

You can add only one issue as a parent to an issue:

  1. Click the issue link to open it in the Issues page.

  2. In the Associations section, in Parent Issue, enter the issue ID or summary text of the parent issue, and select it.

  3. Click Save.

Update Multiple Issues

On the Issues page, you can update multiple issues in a batch to apply the same update:

  1. In the issues list, press the Ctrl key or the Shift key and click the rows of issues.
    You can also use the Space bar and Up-Down arrow keys to select the issues. To select all issues, click Select All.
  2. Click Update Selected.
  3. On the Mass update page, select the check boxes of fields to update and specify their values.

    Note that the Component check box is enabled when its Product is selected.

    The contents of Found In and Release are determined by Product. If Product isn’t specified, the intersection of all known products is used. For example, if product P1 has Found In set to 1.0, 2.0 and product P2 has Found In set to 1.0, 1.5, then with no product specified, the Found In is set to 1.0. The same logic is applied for Release too.

  4. Click Next.
  5. On the Issues will be Updated page, verify the summary, and click Save.

Issues that fail the update are listed with a description of the error. To resolve errors for multiple issues, select the error issues and click Update Selected. You’ll be taken to the Issues Selected page where the previous changes you made are shown.

If all issues are successfully updated, you’ll be returned to the Issues page.

Watch an Issue

You can set up a watch on an issue and get email notifications when a project user updates an issue, adds a comment, or adds or removes an attachment:

Action How To

Issues assigned to you

By default, you get email notifications of issues assigned to you. If you aren’t getting the email notifications, select the Issue updates, attachments and comments check box in your user preferences page:

  1. In the branding bar, click the user avatar, and select Preferences.

  2. Click the Notifications tab.

  3. Select the Issue updates, attachments and comments check box, if not selected.

  4. To the left of the User Preferences title, click Close Close to return to the last opened page.

Issue created by another user

  1. In the branding bar, click the user avatar, and select Preferences.

  2. Click the Notifications tab.

  3. Select the Issue updates, attachments and comments check box, if not selected.

  4. To the left of the User Preferences title, click Close Close to return to the last opened page.

  5. Open the issue in the Issues page.

  6. In the Details section, in CC, enter and select your name.

    You may also enter other names of other users if you want to notify them too.

  7. Click Save.

To stop watching, remove your name from the CC field.

Issues you created but are assigned to another user

By default, you get email notifications of issues created by you. When you create an issue and assign it to another user, your name is set in the CC field of the issue. Open the issue in the Issues page and verify your name in the CC field of the Details section.

To stop watching, remove your name from the CC field.

Use Agile Boards to Manage and Update Issues

The Agile methodology of software development is a type of incremental model that focuses on process adaptability and customer satisfaction. In Oracle Visual Builder Studio (VB Studio), you use the Agile methodology to manage issues in Scrum and Kanban boards.

If you are new to Agile, see http://agilemethodology.org/ for more information.

Before creating a board, appoint a team member as the Agile board’s leader. The leader would be responsible to manage and update issues of the board. The leader could set up team meetings to discuss the progress of issues and then update them in the board.

Here's a summary of the key steps you’d perform as the board’s leader to create and manage issues:

  1. If required, create an issue query that returns issues you’d want to add to the Agile board.

  2. Create an Agile board (Scrum or Kanban).

  3. Configure the working days, progress states, and other properties of the board.

  4. Manage sprints or active issues.

  5. Update progress states of issues.

  6. Review reports and adjust the sprints, issues, or the board accordingly.

Agile Boards Concepts and Terms

Before you start using the Agile boards, it's important that you know about key components and concepts of the Boards page.

Component Description

Board

A Board is used to display and update issues of the project using the Agile methodology. There are two types of boards available: Scrum and Kanban. When you create a board, you associate it with an issue query and the issues returned by the query are added to the board. You can create your own board or use a board created by a team member.

In a board, you update issues by moving them to different progress states of the board. Each progress state has some pre-defined conditions that specify which issues can be assigned to a progress state.

Scrum Scrum

In a Scrum board, tasks are broken small actions to be completed in fixed duration cycles, called as Sprints.

Kanban Kanban

In a Kanban board, tasks are managed with a focus on continuous delivery.

Sprint

A Sprint is a short duration (usually, a week or two) during which your team members try to implement a product component.

You add the product component related issues to a sprint. When you start working on a product component, you start (or activate) its related sprints. To update issues of a sprint, you must first activate the sprint and add the sprint to the Active Sprints view.

Story Points

A Story Point is a metric that defines the relative effort of work and helps to understand how complex the issue is.

Backlog view

In a Scrum board, the Backlog view displays issues of the board, active and inactive sprints of the board, and the sprints from other boards that contain issues matching the board’s query.

Each sprint lists issues added to it. The Backlog section (the last section of the Backlog page) lists all open issues that aren’t part of any sprint yet. The Backlog view doesn’t show the resolved and closed issues.

In a Kanban board, the Backlog view displays active issues (issues being actively worked on) in the Active Issues section and a backlog list of issues (issues aren’t being actively worked on) in the Backlog section. The Epic issues don’t appear in the Backlog view.

Active Sprints view

Available in a Scrum board, the Active Sprints view lists all active sprints of the board and enables you to update an issue status by dragging and dropping it to the respective status columns.

Active Issues view

Available in a Kanban board, the Active Issues view enables you to manage the progress of active issues.

Reports view

Displays various reports and charts that summarize the progress of issues.

Create and Configure Agile Boards

An Agile board contains issues returned by an issue filter. If none of the pre-defined or shared issue filters meet your requirement, create a custom search query and save it as a filter.

Create a Board

You can create a board from the Boards page. When you create a board, you specify the board type, an issue search query, and the estimation criteria.

the project user icon You must be a project member to create a board.
  1. In the navigation menu, click Boards Boards.
  2. Click + Create Board.
  3. In the Create Board dialog box, enter a name and select the board type.
  4. In Search, select the standard or custom issue search query. By default, All Issues is selected.
  5. In Estimation, select the estimation type as Story Points or Estimated Days.
  6. Click Create.

A board is created and issues matching the search query are added to the board, and you’re navigated to the Backlog view. The board’s owner role is also granted to you.

Note that Resolved, Verified, and Closed issues aren’t added to the board. To add new issues to a board, edit the issue search query to reflect the issues in its search result. The issues are automatically reflected in the Backlog list of the board.

You can also create a board from the Switch Board menu. From the board name menu, click + New Board.

After creating a board, you can configure its working days, progress states, and conditions.

Add and Manage Progress States of a Board

A progress state defines the progress of issues in a board. By default, each board has three progress states (To Do, In Progress, and Completed), but you can add more. Each progress state has some pre-defined conditions. A condition defines an issue’s state. You cannot add, edit, or delete a condition.

You can add and manage progress states from the Configure Board page of the board.
  1. Open the board.
  2. From the Board drop-down list, select Configure.
  3. Click the Progress States tab.
Action How To

Edit a progress state

  1. From the progress states list, select the progress state.

  2. To edit the name and description, in Name and Description, enter a new name and description.

  3. To update the capacity (number of issues in the progress state), update the value in Suggested Issue Capacity.

    If the number of issues exceeds the suggested capacity, a warning icon and a message appears in the Active Sprints or the Active Issues view.

  4. To remove a condition, select the condition from the Conditions list, click > and move it to the Unassigned Conditions list.

    To add a condition, select the condition from the Unassigned Conditions list, click < and move it to the Conditions list.

    For example, if you remove the Resolved - WorksForMe from the Completed progress state, issues in the Resolved - WorksForMe state don’t appear in the board.

Add a progress state

A condition can be associated with one progress state only. Before you add a progress state, remove the conditions that you want to apply to the new progress state from their existing progress states.

  1. Click + Add Progress State.

  2. In Name and Description, enter a name and description.

  3. In Suggested Issue Capacity, specify the number of issues to be allowed.

    If the number of issues exceeds the suggested capacity, a warning icon and a message appears in the Active Sprints or the Active Issues view.

  4. To mark the state as the Completed state, select the Completed State check box.

    The check box is disabled if a Completed state exists or the current state isn't the last state in the list.

  5. To add a condition, select the condition from the Unassigned Conditions list, click Move to Conditions the Left Arrow icon and move it to the Conditions list.

  6. To remove a condition, select the condition from the Conditions list, click Move to Unassigned Conditions the Right Arrow icon and move it to the Unassigned Conditions list.

Reorder progress states

In the progress states list, use the Up and Down order buttons to change the orders of the states. The buttons appear when you mouse over the state name. The order of states in the list is reflected in the Swimlanes and Columns views.

The Completed state must be the last state in the list. If Completed isn’t the last state in the list, a Warning the Warning icon icon appear next to the state name. Any changes made to the page aren’t saved until the Completed state is the last state in the list.

Delete a progress state

In the progress states list, mouse over the progress state, and click Delete the delete icon. All conditions of the deleted progress state move to the Unassigned Conditions list and are available to new progress states.

You can’t delete the Completed state, but you can delete other states.

Click Save when you’re finished.

Configure Working Days of a Board

You can configure the working days and non-working of a week by modifying the board’s calendar.

The working and non-working days that you specify affect the output of the Sprint Report, Issues Report, and the Burndown Chart.
  1. Open the board.
  2. From the Board drop-down list, select Configure.
  3. Click the Working Days tab.
  4. On the Configure board page, specify standard working and non-working days.
    • In Standard Working Days, select or deselect the check boxes of the working weekdays.

    • In Non-Working Days, click + Add to add a non-working date (such as a holiday). From the calendar, select the date.

      To edit a non-working day, select it from the list, and select the new date in the calendar.

    • Select (or deselect) the Show Non-Working Days in Sprint Report Chart check box to show (or hide) the non-working days in the sprint reports.

      If selected, the non-working days appear in gray at the top in the burndown charts.

  5. Click Save.
Configure and Manage a Board

From the Board menu, you can select options to configure, duplicate, and delete the board. From the Configure Board page, you can edit and update the name, description, associated issue search query, and estimation criterion of a board.

Action How To

Edit a board’s name and description

  1. From the Board drop-down list, select Configure.

  2. In the General tab, in Name and Description, update the values.

  3. Click Save.

Edit the board’s search query and estimation

  1. From the Board drop-down list, select Configure.

  2. In the General tab, in Search select the search query. In Estimation, enter the new estimation value.

  3. Click Save.

Enable or disable time tracking

If the time tracking is enabled, then the Active Sprints page shows the estimation in Remaining Days only. The Backlog page shows the estimation in Remaining Days if estimation metric is Estimated Days.

If the time tracking is disabled, then the Backlog, Active Sprints and Reports pages show the chosen metric for Estimation (estimated days or story points) instead of Remaining Days and Time Spent.

  1. From the Board drop-down list, select Configure.

  2. In the General tab, in Time Tracking, select On or Off to enable or disable time tracking.

  3. Click Save.

Create a copy of a board

To create another board with similar properties of an existing board that you can access, instead of creating a new board and manually copying properties, you can create a copy of the board. The copied board has properties include time tracking, progress states, and working days.

  1. From the Board drop-down list, select Copy Board.

  2. In the Copy Board dialog box, click Copy.

Delete a board

You can’t delete a Scrum board with active sprints. You must complete the active sprints before you delete the board. You can delete a Kanban board with active issues or archives. All issues of the deleted board are returned to the backlog.

  1. From the Board drop-down list, select Delete Board.

  2. In the Delete Agile Board dialog box, select the I understand that my agile board will be permanently deleted check box and click Delete.

Use Scrum Boards

Using a Scrum board, you manage and update issues using sprints.

A Scrum board has three views: Backlog, Active Sprints, and Reports. The Backlog view lists all active and inactive sprints of the board, and a backlog list of issues. The Active Sprints view enables you to manage the progress of issues of an active sprint. The Reports view displays various issue reports.

Create and Manage Sprints

You can create and manage sprints from the Backlog view of a Scrum board. You must be a project owner or the board owner to create, edit, update, or delete a sprint.

When an issue is assigned to a sprint, the sprint is displayed in all boards whose issue query returns any issue of the sprint in its result. You might find such sprints in your board. Note that you can’t edit or start sprints that you didn’t create, or sprints that weren’t created in the current board.

If there are no issues assigned to a sprint, the sprint is available only in the board in which it was created.

Action How To

Create a sprint

  1. From the toggle buttons, click Backlog.
  2. In the Backlog view, click + Add Sprint.

  3. In the Add Sprint dialog box, enter the sprint name. If the Scrum board uses story points, then specify the sprint’s capacity.

  4. Click OK.

Edit a sprint

  1. From the toggle buttons, click Backlog.
  2. In the Backlog view, for an inactive sprint, click ... and select Edit sprint.

    If the sprint is active (or started), click Edit Sprint.

  3. In the Edit Sprint dialog box, you can update the sprint’s name, board, start and end dates, and its capacity in story points.

    The Story Points field is available if story points were selected as the estimation for the board.

  4. Click OK.

Start a sprint

When you or your team begin work on a sprint and want to update the issues of the sprint, you must first start (or activate) it.

  1. From the toggle buttons, click Backlog.
  2. In the Backlog view, for the sprint that you want to start, click Start Sprint.

  3. In the Start Sprint dialog box, specify the start and end dates of the sprint.

    If necessary, update the sprint’s name and its estimate.

  4. Click Start.

The started sprint is now available in the Active Sprints view.

Reorder a sprint

In the Backlog view, by default, the inactive sprints (also called as future sprints) in the order they were created. You can change their display order manually.

For the inactive sprint that you want to move up or down, click ... and select Move sprint up or Move sprint down.

You cannot change the order of active sprints. The active sprints are ordered by Start Date in the Backlog view. If two sprints have the same Start Date, then they are ordered by name.

Move a sprint to another board

  1. From the toggle buttons, click Backlog.
  2. In the Backlog view, for an inactive sprint, click ... and select Edit sprint.

    If the sprint is active (or started), click Edit Sprint.

  3. In the Edit Sprint dialog box, from the Board drop-down list, select the target board.

  4. Click OK.

Delete a sprint

You can delete an inactive sprint from the Backlog view of the board. You can’t delete an active sprint.

For the inactive sprint that you want to delete, click the ... and select Delete Sprint. The sprint is deleted and all issues of the sprint are moved to the Backlog list.

Add and Manage Issues in a Sprint

From the Backlog view, you can drag-and-drop issues to add or remove them from a sprint.

When you add or remove issues from a sprint, keep a close eye on the sprint's capacity . If the sprint's total story points for issues exceed the sprint's story points capacity, you'll see a warning message. If this happens\, you can either increase the sprint's capacity or move some issues to another sprint.

Here's how to manage issues in a sprint:

Action How To

Add an issue to a sprint

  1. From the Backlog list or from the sprint that contains the issue, drag the issue to the target sprint.

  2. In the blue dotted rectangle that appears when you drag the issue to the target sprint, drop the issue in the blue rectangle.

You can also right-click the issue and select Send to > target sprint name to move the issue to the target sprint. A Sprint field is also added to the issue indicating the sprint it’s associated with.

If you’re unable to use the drag-and-drop action, click the issue link to open it in the Issues page. Navigate to the Agile section. From the Added To drop-down list, select the sprint.

Create an issue from the sprint

In the sprint, below the issues table, click New Issue. On the New Issue page, enter the issue’s details, and click Create Issue.

The new issue is automatically associated with the current sprint.

Remove an issue from a sprint

  1. From the sprint that contains the issue, drag the issue to the Backlog list.

  2. In the blue dotted rectangle that appears when you drag the issue to the Backlog list, drop the issue in the blue rectangle.

You can also right-click the issue and select Send to > Backlog to remove the issue from the sprint.

If you’re unable to use the drag-and-drop action, click the issue link to open it in the Issues page. Navigate to the Agile section. In the Added To field, click the remove icon.

Update Issues in an Active Sprint

You can use the Active Sprints view to manage the progress of issues in an active sprint.

You can use either the Swimlanes view or the Columns view to see the issues in an active sprint. The Swimlanes view displays issues categorized by issue owner (the member to whom the issue is assigned). For each issue owner, issues are grouped in vertical progress (or status) columns.

The Columns view displays issues grouped in vertical progress columns.

By default, each board contains three columns: To Do, In Progress, and Completed. If you need to, you can use the Configure Board page to add more progress columns to the board.

Update an Issue’s Progress in an Active Sprint

You can update an issue’s progress in the Active Sprints view by dragging it from one progress column to another.

If you’re unable to use the drag-and-drop action, click the issue ID to update its progress from the Edit Issue page.

  1. Open the board that owns the active sprint.
  2. Click Active Sprints.
  3. Select the issue list view: Swimlanes or Columns.
  4. To update an issue’s progress, drag and drop it from one column to another.
    For example, when a team member starts work on an issue, drop the issue to the In Progress column (if exists).
  5. In the Change Progress wizard, from the To drop-down list, select the new status of the issue. If necessary, enter a comment in the Comment field.
    If you want to update the time spent on the issue, click Next.
  6. Click OK.

If the board uses story points, the number to the right of the column name is updated. An activity is also added to the History tab of the issue’s Activity section.

Update Time Spent on an Issue

When you move an issue from one state to another, you can also update the time spent on the issue in the Change Progress wizard.

In the Add Time Spent page, in Time Spent, specify the number of days you’ve spent on the issue. In Remaining, use the default Reduce remaining ... days by entered Time Spent option to automatically subtract the value specified in Time Spent from the existing value of Remaining, if Remaining was set previously.

If Remaining was not set, then the value specified in Time Spent is subtracted from Estimate. The option is disabled if the Estimated field isn’t set.

To specify the remaining days manually, select the Set to option and specify the remaining days.

Reschedule a Sprint

While updating issues of a sprint, you can change the start or end date of the sprint, or update its capacity from the Edit Sprint dialog box.

  1. In the Backlog view, for the sprint you want to reschedule, click Edit sprint.
  2. In the Edit Sprint dialog box, change the start and end dates.
    To update the sprint’s capacity, update Story Points . The field is available if story points were selected as the estimation of the board.
  3. Click OK.
Complete a Sprint

You can complete a sprint from the Active Sprints view of the board.

You must be a project owner or the board owner to mark the sprint as completed.
  1. Open the board the sprint belongs to.
  2. Click Active Sprints.
  3. In the sprint drop-down list on the left, select the sprint.
  4. Click Complete Sprint.
  5. In the Complete Sprint dialog box, select the I understand that it will be removed from the Active Sprint view check box, and click Complete Sprint.
After a sprint is complete, it’s removed from the Active Sprints view. A warning displays if there are any incomplete issues in the sprint. All incomplete issues go back to the next inactive sprint, or to the Backlog section if there are no inactive sprints. The Sprint Report page opens showing the day-by-day progress of the sprint issues.
Review Issue Reports for a Scrum Board

Several differengt kinds of reports are available in the Reports view of a Scrum board:

This Kind of Report Displays ...

Burndown chart

The amount of unfinished work in a sprint or in an epic

Cumulative Flow chart

The total number of issues in each of the board's progress states, over time

Control chart

Information about an issue’s progress state change events on the timeline

Sprint report

A sprint's complete, incomplete, and open issues

Epic report

An epic's complete, incomplete, and open stories

Velocity report

A velocity chart for completed sprints

See Review Agile Reports and Charts.

Use Kanban Boards

Using a Kanban board, you manage issues using Active issues.

A Kanban board has three views: Backlog, Active Issues, and Reports. The Backlog view lists active issues (issues that’re being actively worked on) and a backlog list of issues (issues aren’t being actively worked on). The Active Issues view enables you to manage the progress of active issues. The Reports view displays various issue reports.

Add and Manage Active Issues

From the Backlog view, you can add issues to or remove issues from the Active Issues list using drag-and-drop actions.

When you add or remove issues from the Active Issues list, keep a watch on its capacity. If the total story points of active issues are more than the story points capacity of the board, a warning message appears. In such a case, you can either increase the capacity of the board or remove some issues from the Active Issues list.

Action How To

Activate an issue

  1. From the Backlog list, drag the issue to the Active Issues section.

  2. In the blue dotted rectangle that appears when you drag the issue to the Active Issues section, drop the issue in the blue rectangle.

In the Backlog list, you can also right-click the issue and select Send to >Active Issues to move the issue to the Active Issues list. Issues already added to sprints of Scrum boards aren’t available in the Kanban board Backlog list.

If you’re unable to use the drag-and-drop action, click the issue link to open it in the Issues page. Navigate to the Agile section. From the Added To drop-down list, select the Active Issues option under the board name.

Create an issue from the Active Issues section

In the Active Issues section, below the issues table, click New Issue. In the New Issue page, enter the issue’s details, and click Create Issue.

The new issue is automatically activated and associated with the Kanban board.

Remove an issue from the Active Issues list

  1. From the Active Issues section, drag the issue to the Backlog list.

  2. In the blue dotted rectangle that appears when you drag the issue to the Backlog list, drop the issue in the blue rectangle.

You can also right-click the issue and select Send to > Backlog to remove the issue.

If you’re unable to use the drag-and-drop action, click the issue link to open it in the Issues page. Navigate to the Agile section. In the Added To field, click Remove the remove icon.

Update Active Issues

The Active Issues view enables you to manage the progress of active issues.

You can use either the Swimlanes sub-view or the Columns sub-view to view the active issues. The Swimlanes sub-view displays issues categorized into issue owners (member whom the issue is assigned to). For each issue owner, the issues are categorized into vertical progress (or status) columns. The Columns sub-view displays the issues categorized into vertical progress columns.

By default, each board contains three columns: To Do, In Progress, and Completed. If required, you can add more progress columns to the board from the Configure Board page.

From the Active Issues view, you can update an active issue’s progress state and archive the completed issues.

Update the Progress State for an Active Issue

You can update an active issue’s progress in the Active Issues view by dragging it from one progress column to another.

If you’re unable to drag-and-drop the issue, click the issue ID and update its progress from the Edit Issue page.

  1. Open the board that owns the active issues.
  2. Click Active Issues.
  3. Select the desired issue list view: Swimlanes or Columns.
    If necessary, use the sort list boxes to sort the active issues.
  4. To update an issue’s progress, move it from one column to another.
    For example, when a team member starts work on an issue, move the issue to the In Progress column (if exists).
  5. In the Change Progress wizard, from the To drop-down list, select the new status of the issue. If necessary, enter a comment in the Comment field.
    If you want to update the time spent on the issue, click Next.
  6. Click OK.
An activity is added to the History tab of the issue’s Activity section.

Update Time Spent on an Issue

When you move an issue from one state to another, you can update the time spent on the issue in the Change Progress wizard.

In the Add Time Spent page, in Time Spent, specify the number of days you’ve spent on the issue. In Remaining, use the default Reduce remaining ... days by entered Time Spent option to automatically subtract the value specified in Time Spent from the existing value of Remaining, if Remaining was set previously.

If Remaining was not set, then the value specified in Time Spent is subtracted from Estimate. The option is disabled if the Estimated field isn’t set.

To specify the remaining days manually, select the Set to option and specify the remaining days estimate.

Archive Completed Issues

You can create an archive of all issues listed in the Completed progress state from the Active Issues view of the board. The archived issues are then removed from the Active Issues view.

Before you archive completed issues, make sure that all parent and child issues are moved to the Completed progress state before you create an archive. An error is reported if the Completed progress state contains a completed parent issue with an open child issue, or a completed child issue with an open parent issue.
  1. Open the board.
  2. Click Active Issues.
  3. Verify the issues list in the Completed progress state.
    Note that the list may include some issues that’re filtered out of the display of the current Active Issues view by the board’s query.
  4. Click Archive Completed Issues.
  5. In the Archive Completed Issues dialog box, in Archive Name edit the archive name (by default it is Archive <date-time stamp>) if required, verify the list of issues in the Completed progress state, select the I understand that the archived issues will be removed from the Active Issue view check box, and click Archive Issues.
    If you edited the default archive name, make sure that it’s unique across all Kanban boards and Scrum sprint names. The name must not be longer than 255 characters.
The completed issues are archived in the specified archive name and the Issues Report of the archive opens in the Reports view.
Review Issue Reports for a Kanban Board

Several kinds of reports are available in the Reports view for a Kanban board:

This Kind of Report Displays ...

Burndown chart

The amount of unfinished work in issues or in an epic

Cumulative Flow chart

The total number of issues in each of the board's progress states, over time

Control chart

Information about issue’s progress state change event on the timeline

Issues report

Active and archived issues.

Epic report

An epic's complete, incomplete, and open stories

Velocity report

A velocity chart of completed issues

See Review Agile Reports and Charts.

Review Agile Reports and Charts

Several kinds of reports and charts cab be used with your Scrum and Kanban boards:

  • Burndown charts
  • Sprint reports
  • Issues reports
  • Epic reports
  • Velocity reports
  • Cumulative flow charts
  • Control charts
Burndown Charts

Burndown charts show how much work still needs to be completed in issues or epics.

The burndown chart for issues and epics is available in Scrum and Kanban boards:

  1. Open the board.

  2. Click Reports.

  3. Click Issues Issues or Epic Epic.

  4. Click the Burndown Chart tab.

Scrum Boards

For a Scrum board, the chart for your active sprint is displayed.

  • To use a different sprint, click the Sprint drop-down.

  • To use a different estimate criterion, click the Burndown drop-down and select from Estimated Days, Story Points, or Number of Issues. The Y-axis in the chart reflects this setting.

The burndown chart displays the configured tracking statistic for the active sprint, start and end dates, the sprint capacity, and a guideline for completing the statistic you’re tracking in the sprint. The horizontal axis tracks time; the vertical axis represents your configured tracking ttatistic, either story points, estimation days, or number of issues. Use burndown charts to see the total work remaining and increase the accuracy for predicting the likelihood that you'll achieve the sprint's goal. By tracking the remaining work throughout the iteration, your team can manage its progress and respond appropriately, especially if things don’t go as planned. If time tracking is enabled for the board, the burndown chart always shows the number of remaining days and the amount of time spent.

A burndown chart includes all of the sprint's issues, those that’ve been completed as well as those that are still being worked on. Mapping the status for these issues to your board determines when an issue is considered completed or not completed.

The bottom of the page shows a history, a table of events associated with the issues, including issues that still haven't been completed.

Kanban Boards

For a Kanban board, the chart displays your active issues. To see issues for an archived version, click the Issues list and select the desired one.

The burndown chart displays the configured tracking statistic for the active issues. The horizontal axis tracks time; the vertical axis represents your configured tracking statistic, either story points, estimation days, or the number of issues. Use burndown charts to see how much work remains to be done. This will increase your ability to accurately predict the likelihood that you'll achieve the goal. By tracking the remaining work throughout the iteration, your team can manage its progress and respond appropriately if things don’t go as planned. If you enable time tracking for the board, the burndown chart always shows the number of days remaining and the amount of time spent thus far.

The burndown chart includes all issues, those that have been completed and those that are still pending. Mapping these statuses to your board determines when an issue is considered completed or not completed.

The bottom of the page shows a history, a table of events associated with the issues, including issues that still haven't been completed.

Sprint Reports

Sprint Reports show completed and open (not yet completed) issues in a sprint.

Sprint Reports are available for sprints in Scrum boards only:

  1. Open the board.

  2. Click Reports.

  3. If necessary, click Sprint.

  4. Click the Sprint Report tab. The Sprint Report chart for your active sprint is displayed.

    • To select a different sprint, select it from the Sprint drop-down list.

    • To select a different estimate criterion, select Estimated Days, Story Points, or Number of Issues from the Burndown drop-down list. The Y-axis in the chart reflects this setting.

A Sprint Report provides a day-by-day progress report, with much of the same information that’s in the burndown chart, although in a slightly different format. The Sprint Report shows the list of issues in each sprint. It provides useful information for your Sprint Retrospective meeting and for mid-sprint progress checks. Mapping the statuses to your board determines when an issue is considered completed or not Completed. If you enabled time tracking for the board, the Sprint Report chart shows the number of days remaining in the sprint and the amount of time spent to date.

At the bottom of the page, the Sprint Report displays tables that show completed, open, and removed issues.

Issues Reports

Issues Reports show active and archived issues.

The Issues Report is available for issues in Kanban boards only:

  1. Open the board.

  2. Click Reports.

  3. If necessary, click Issues Issues.

  4. Click the Issue Report tab. The Issue Report chart for active issues is displayed.

    To select a version that shows archived issues, click the Issues drop-down list and select the desired option.

An Issues Report provides a day-by-day progress report with much of the same information found in a burndown chart, although in a slightly different format. An Issues Report lists active and completed issues. If you enabled time tracking for the board, the Issue Report chart shows the number of days remaining in the sprint and the amount of time spent to date.

At the bottom of the page, the Issues Report displays a table of issues. If you select Active Issues (default) in the Issues drop-down list, the table lists completed and non-completed issues. If you selected an archive instead, the table lists only completed issues.

For each issue, the report shows the original estimate value and modified values in Estimated Days (or Story Points).

Epic Reports

Epic Reports show which of the epic's stories have been completed and which are still open (not completed).

The Epic Report is available in Scrum boards and Kanban boards for epics:

  1. Open the board.

  2. Click Reports.

  3. Click Epic Epic.

  4. Click the Epic Report tab.

For Scrum Boards

The Epic Report Chart for your active sprint is displayed.

  • To select a different epic, select it from the Epic drop-down list.

  • To select a different estimate criterion, select Estimated Days, Story Points, or Number of Issues from the Burndown drop-down list. The Y-axis in the chart reflects this setting.

An Epic Report provides a day-by-day progress report with much of the same information that’s in the burndown chart, although in a slightly different format. An Epic Report lists the stories (or sub-issues) in each epic. It provides useful information for your Epic Retrospective meeting and for mid-sprint progress checks. Mapping statuses to your board determines when a story is considered completed or not. If you enable time tracking for the board, the Epic Report chart shows the number of days remaining and the amount of time spent to date.

At the bottom of the page, the Epic Report displays tables of completed, open, and removed stories.

For Kanban Boards

The Epic Report Chart for your active issues is displayed. To select an archived issue version, click the Issues list and select the desired version.

An Epic Report provides a day-by-day progress report with much of the same information that’s in the burndown chart, although in a slightly different format. An Epic Report lists the stories (or sub-issues) in each epic. It provides useful information for your Epic Retrospective meeting and for progress checks. Mapping statuses to your board determines when a story is considered completed or not. If you enable time tracking for the board, the Epic Report chart shows the number of days left in the epic and the amount of time spent to date.

At the bottom of the page, the Epic Report displays tables of completed, open, and removed stories.

Velocity Reports

Velocity Reports show velocity charts for completed sprints.

Velocity Reports are available for Scrum boards only:

  1. Open the board.

  2. Click Reports.

  3. Click Velocity Velocity.

  4. From the Estimation drop-down list, select Estimated Days, Story Points, or Number of Issues.

  5. Depending on the value selected in Estimation, a Velocity Chart is displayed for committed and completed values.

    If you selected Story Points in the Estimation drop-down list, the chart will also display the Suggested Capacity for each sprint as a dashed horizontal line.

A Velocity Report includes a Velocity chart, showing a graph of the last seven completed sprints for the selected estimation. It also shows a table that lists completed sprints, the number of issues in each sprint, estimated values committed, and estimated values completed. Active sprints aren’t shown or listed.

You can use the Velocity Report to plan the amount of work that can be committed to future sprints. Managers can see whether the team met the original estimation and can plan the effort required for new or future sprints.

At the bottom of the page, there is a sprint table, whose columns are determined by the value you selected in the Estimation drop-down list.

Cumulative Flow Charts

Cumulative Flow Charts display the total number of issues for each of the board's progress states over time.

Cumulative Flow Charts are available in Scrum boards and Kanban boards for issues only:

  1. Open the board.

  2. Click Reports.

  3. If you are using a Scrum board, click Sprint Sprint. If you’re using a Kanban board, click Issues Issues.

  4. Click the Cumulative Flow Chart tab.

Scrum Boards

A Cumulative Flow Chart displays the total number of issues in each of the board's progress states over time for the active sprint. The issues that are listed in the chart are the same issues that the Sprint Report displays.

These events can change the number of issues in a progress state:

  • An issue is added to the sprint

  • An issue is removed from the sprint

  • An issue’s progress state in the sprint changes because its status or resolution changes

The Configure Board page shows the progress states that correspond to the board's current list. The chart is a stacked area chart that enables you to see the number of issues in each progress state and the total number of issues in the sprint at any given point on the timeline. The color for each progress state is randomly assigned. By clicking the progress state names in the chart legend, you can show or hide them. The events table has a column for each progress state and shows the number of issues for each progress state that’s affected by the event.

Kanban Boards

A Cumulative Flow Chart displays the total number of issues in each of the board's progress states over time for the Active Issues or an archive. The issues listed in the chart are the same as those that are displayed in the Issues Report.

These events can change the number of issues in a progress state:

  • An issue is added to active issues or an archive

  • An issue is removed from active issues or an archive

  • An issue’s progress state in active issues or an archive changes because its status or resolution was changed

The Configure Board page shows the progress states that correspond to the board's current list. The chart is a stacked area chart that enables you to see the number of issues in each progress state and the total number of issues in the sprint at any given point on the timeline. The color for each progress state is randomly assigned. By clicking the progress state names in the chart legend, you can show or hide them. The events table has a column for each progress state and shows the number of issues for each progress state that’s affected by the event.

Control Charts

Control charts show progress state changes to issues on a timeline.

Control charts are available in Scrum boards and Kanban boards for both Sprint reports and Issues reports. A Control chart is a scatter chart with each point representing an event where a progress state changed on the timeline. This event occurs when an issue moves from one progress state to another.

Here's how to create a Control chart

  1. Open the board.

  2. Click Reports.

  3. If you are using a Scrum board, click Sprint Sprint. If you are using a Kanban board, click Issues Issues.

  4. Click the Control Chart tab.

The Y-axis of the chart shows how many days an issue spent in its previous progress state (the progress state from which the issue was moved). For example, if an issue's status was changed on Jan 10 from To Do to In Progress, the chart displays a point on Jan 10 and the Y-axis shows the number of days the issue was in the To Do progress state.

The colors for the progress states are randomly assigned. You can show or hide the progress state points by clicking on the names of the progress states in the chart legend. Click the chart legend to display a line on the chart that shows the average number of days spent in a progress state.

The events table has a column for each progress state in the board, with values representing the number of days spent in the progress state at the time of each event. The table displays the average number of days a little differently than the chart does.