VersionOne - Quick Guide

VersionOne - Introduction

VersionOne is a web-based project management tool used by testers, developers and other stake holders to manage, track and organize software testing efforts. It follows and covers full life cycle of Agile Methodologies. It supports from first step as Product Backlog to the project’s final step as completion and delivery.

Interesting Points

VersionOne supports a wide range of functionalities and is one of the best available project management tools for Agile. VersionOne is joining CollabNet to bring DevOps into the table.

Following are a few interesting facts about VersionOne −

VersionOne helped to bring the Agile Management tool in 2002.
VersionOne is also known as the Agile Management tool.
It is developed and copyright by VersionOne Inc.
VersionOne is a web based tool that supports all browsers especially Chrome, Firefox, IE etc.
It supports different windows OS like Windows XP, Vista, 7, Mac, etc.
VersionOne provides 30days trial period.
It supports all phases of planning, scheduling, collaborating, tracking and reporting for projects, releases, iterations, epics, stories, defects, tasks, tests, teams and team members.
VersionOne was named as one of the Best Places to Work by the Atlanta Business Chronicle.
Now, CollabNet and VersionOne have merged to accelerate innovation across Enterprise Software Development and Delivery in 2017.
VersionOne can be customized using various methodologies such as SAFe, Scrum, Kanban, Lean, XP, and DAD.

License and Free Trial

VersionOne is used at commercial level across various software industries. It allows the new users to go through the tool by providing limited free access. In this section, we will see how VersionOne connects with different user groups at personal and commercial level −

VersionOne is a commercial tool and available as Trial version for a limited period of 30 days. For personal use, a user can register and get a hands-on experience of VersionOne.
To utilize VersionOne services, a license is required. After 30 days, if a user wants to continue using VersionOne, a license is required. By purchasing one of the products, VersionOne provides license key to continue for a certain time period based on purchase agreements.
VersionOne provides free license for 30 days for cloud based access as well as local server set up. User can set up host server into his local machine as well by following installation guidelines and fulfilling pre-requisite.

VersionOne Uses

There are a wide range of benefits and usage of VersionOne depending on team size, type of work and other factors. The benefits and usage are listed below −

VersionOne is used in tracking all QA activities from the 1st phase of software testing lifecycle in Agile. Tracking can be started from adding the requirements to accepting the requirement by the Product Owner.
VersionOne is useful in Project Management, Defect Management and to customize into different agile methodologies as per the requirements. A user with proper role can customize the VersionOne fields, boards, reports, displays according to project requirement and standards.
In addition to the above, VersionOne also supports agile portfolio management, product road mapping, regression test management, customer idea management, agile visualizations and custom reporting and analytics.
It supports all macro level activities performed by QA.
VersionOne is very useful in performing QA tasks like planning, scheduling, collaborating, tracking and reporting for projects, etc.

VersionOne Specifications

The base of VersionOne is combined with different and latest technologies and ideas. To use a developed VersionOne tool, hardware and software supports are required at Server as well as Client side. Following table lists down important specification of VersionOne −

Sr.No.	Specification	Description
1	Application copyright	It is taken by VersionOne Inc. It provides Commercial and Trial Version.
2	Tool scope	It can be used as Project Management and defect tracking It is utilized as Agile Management Tool
3	Testing Methods	Agile Testing Automation testing Exploratory Testing Functional/Manual Testing
4	Tool Objectives	Complete life cycle of Agile Methodologies Desktop Testing Web Testing Report statistics
5	Management Features	Product Backlog Resource Management Defect Management Project Management in Agile Reporting
6	Hardware Requirements for Server	CPU: Dual Core 2GHz and latest Memory : 4GB and aboveRAM
7	Error Handling	Capture screenshots
8	User interface Available	Plugin GUI usability Mobile UI Server and Web based

VersionOne - Features

In this chapter, we will discuss the different features of VersionOne. The main feature of VersionOne is to attract QAs and other stakeholders for Agile management.

VersionOne Core Features

VersionOne provides a wide range of features that prove beneficial to the Agile Project team. It does not only support Project management but also how to do day to day activities in case team is not situated locally. It provides a software solution to implement agile within the globally situated team.

Following table lists down the core features of VersionOne −

Sr.No.	Core Features	Description
1	Testing Supports	VersionOne supports the following test methodologies − Agile Testing − Full Life Cycle Black box testing Exploratory Testing Functional/Manual Testing Automation Testing
2	Centralize & organize	VersionOne tool can create, centralize, organize and manage test cases very effectively and efficiently. It can easily import test cases from Excel and other management tool. It can create multiple versions of test cases for comparison and uses It can do planning of releases and sprints.
3	Manage & Track Progress	It supports build out and re-run of test execution suites. It kicks off automation suite as well. It captures step-by-step progress of sprint/release with detailed explanation. It supports day-to-day progress and individual contribution.
4	Notification	Email can be sent for a particular task/communication to users. Voting and watching features to keep an eye on progress for stakeholders. Use @mention to get attention of specific team member at Comments/Description.
5	Power Search	VersionOne supports powerful search functionality with Hotkeys features. Supports free text search. Supports syntax search.
6	Reports	VersionOne supports multiple reporting. It supports Burndown, Velocity and Test Trends report. Generate detailed summary report for projects, release and sprints. Track the workload of entire team as well as individual. It supports Cross Project Report as well.
7	Scale with Team Growth	VersionOne supports any business team and any project irrespective of size and complexity.
8	Integration	VersionOne supports more than 80 pre-built integration to connect with different software’s to make work easy. Wide range of add-ins makes it universal across the globe – JIRA, BugZilla, ALM, GitHub, Borland, CA, Hudson, Jenkins, Visual Studio etc. It also supports Salesforce, Microsoft, Zendesk.
9	Common Features	It supports sticky sidebars. It supports rich text formatting. It helps in optimizing printing. It helps in scheduling and forecasting.
10	Recover Data	It helps in generating and downloading full system backups. Migrate and import existing test cases from Excel and legacy data tool. Export data into CSV, XML and Excel files.

VersionOne - Free Trial Access

VersionOne provides free trial for 30 days to registered users. The free trial version of VersionOne comes with basic features. TestRail has other plans as well with different advanced features and add-ins. The cost depends on the products that come along.

VersionOne has the following different products −

Team
Ultimate
Catalyst
Enterprise

VersionOne Team is free for Single Team with basic features for other products VersionOne provides 30days trial period.

By visiting https://www.versionone.com/product/lifecycle/pricing-and-editions/ a user can see the different available plans for trying purpose.

Setup for Free Trials

To use the free trial version, one time basic setup is required. It includes registering into VersionOne by providing basic details and getting personal URL at email to access the VersionOne.

In the following steps, we will learn how to set up the VersionOne while accessing it for the first time −

Visit https://www.versionone.com/ and click on Try Free at the top right as shown in the following screenshot −

It opens a basic form to create a VersionOne account.

Enter the details at following fields as shown in the following screenshots −
- Name, Organization, Designation, Number and Country. These are basic details of user and useful to set up profile after accessing the VersionOne. These details help to maintain unique user concept. A user cannot enter duplicate records to register.
- Email − Please note, it accepts gmail, yahoo, outlook. It can be business email as well.

After entering all the details, check the checkbox for Term & Services and click on “Start Your Free TRIAL”.

It will display the next page where a user should create password and provide Project/Sprint name. Now, click on Set Up.

Upon clicking Set Up, VersionOne creates the personal URL and account to access free trial and send the email, provided into the form at the 1^st page.

An Email will look like as in the following screenshot −

By visiting the given URL, a user will get login page for VersionOne.

VersionOne - Login

In this chapter, we will learn the steps involved to log into VersionOne.

Follow these steps to log into VersionOne.

Step 1 − To login into VersionOne, go to your sample website, provided into email while creating the free trial. It will open a login page.

Step 2 − Enter your registered email address as Username and Password (selected while creating the account).

Step 3 − Click on the Login button.

Following screenshot shows how to login into VersionOne using credentials −

On Error

While logging in, a user can face errors due to wrong combination of username/password. A user can utilize different available features to reset password and login again. Here, we will see what errors a user can face and how to find resolution to such instances −

Due to unsuccessful login, a page as shown in the screenshot below might appear.
Error may occur due to wrong combination of email id or password.

Following screenshot shows the error message a user receives if the credentials are not correct −

If you forgot the password, to recover it −

Click on “Forget Password” beside the Login button.
Enter the Login Email.
Click on the Reset Password button. It asks to enter registered email to send the password reset link.

The following screenshot shows how to recover the password if you forgot −

A user will get an email with details to reset the password.

On Successful Login

In this section, we will discuss how VersionOne works on successful login.

On successful login, the My Subscription page gets displayed. The following screenshot displays the welcome page of VersionOne on successful login

VersionOne - Dashboard

After logging into VersionOne, a user can navigate to Dashboard where progress of work is summarized and a user can customize reports and matrices as well. A Dashboard is customized by Admin. Based on roles, admin can set the access of VersionOne. Dashboard is similar to homepage that displays all important details and provides links to access of other modules. In this chapter, we will see features and customization of Dashboard.

Points to Note

By default, the Dashboard provides important details about project and the progress. It displays the data for different modules like Project Hierarchy, number of Open Issues, Backlog Count, Defects at project level in the hierarchy. In the following section, we will discuss the important features of Dashboard −

To navigate to the My Dashboard page, click on My Home → My Dashboard link as shown in the screenshot below. It displays the Dashboard page with the default set up.

In the Dashboard page, My Project Summary is located at the top of the page. It shows different metrics to evaluate the state of a project. Filters are also available to search specific projects details. By default, the following fields display for each project −

Project Title
Owner
End Date
Projected End Date
Progress Bars (hover to see Open and Closed Estimates)
Open Stories/Backlog Items
Open Defect Count
Open Issue Count
The navigation bar, present at the top of the page, will be same across all pages/screen of VersionOne – Project, Portfolio, Product, Release and Team. The navigation bar has many sub links under each of these links. At the right side of the same navigation bar, Report section is also available. By clicking on these links and sub links, a user can get access to different modules/features supported by VersionOne
Dashboard has different links at the top right. These are same across all pages – Site Navigator, Settings, User Profile and Help. These are the static feature of the VersionOne HTML design.
In the extreme left side, it displays few useful shortcut links as Add New Item for Backlog Item, Defect, Story, etc., My Recent Changes to view all recent changes, Rooms, Timesheet, Collaboration, Conversations, Topics and Deleted items. The following screenshot displays the Dashboard of VersionOne −

Add Chart

Dashboard can be customized by adding different available charts to track day to day progress of the project/sprint. A user can add any of the following charts to the My Dashboard page. These charts (displayed at the bottom of the page) help to track progress of the project, sprint/iteration, and team status.

Project Burndown
Sprint/Iteration Burndown
Work item Trend
Defect Priority Trend
Defect Priority Trend
Test Trend
Work item cycle time
Work item cumulative flow

To add a chart, click on the Add Chart button present at the My Dashboard page and select one of the charts as shown in the screenshot below. It displays all available charts to add into the dashboard.

After selection, the chart appears at the bottom of the page as shown below −

User Profile

A logged in user can view his profile in VersionOne. A user with admin role will have access to all users’ profiles and can edit/update as well. In this section, we will discuss how to view profile and update the details.

By clicking on the Profile icon, a user can view the following options −

My Details − user can view his personal profile as shown below −

It opens the profile details with the edit button on the right side. A user can view History and type of application by clicking on corresponding tab. In details, a user can see Project Membership, Owned Projects, Link and Attachments as well.

The following screenshot displays the user detail page −

Edit the details on this page.

Once a user clicks on the Edit button, the user details open in a new window in the edit mode. A user can change the details and click on Save to save the changes as shown below −

Lifecycle Preferences − A user can select Navigation, Email forwarding options, Event Notifications and Report Settings as shown in the screenshot below −

Change Password − Using this option, user can change the current password and set a new one.
Push Notifications − It manages notification from third party applications.
Applications − It manages keys and tokens from third party applications.
Logout − By clicking on Logout, a user will be get back to the login page and will not be able to access project details without logging in back as shown in the screenshot below.

VersionOne - Invite Users

VersionOne supports the invitation functionality. A logged in user can invite any number of users to join VersionOne. A user with Admin role can directly add the user into VersionOne. In this chapter, we will see steps about how to invite the user.

Follow these steps to invite new users into the VersionOne domain −

Navigate to the Setting icon present at top right of each page and select Members as shown in the screenshot below. It opens the Member’s page with the user’s details.

Login as System Admin is a prerequisite to view this option.
The Members’ page that opens up displays a list of members having the domain access.
At the right side, a user can view the Invite Member button where a user can select either Invite member or Add Member.
Invite Member − A user gets email to join the VersionOne
Add Member − The Admin provides Username and Password to add one of the team members who already has access to VersionOne for different domain. It is basically allowing access of the project to a team member

The following screenshot displays the Invite Member option −

The following screenshot displays the Invite Members form where the Admin enters email of the invited member, the project to assign and the role to offer. After selecton, click on the Invite Members button.

The user will receive the email to join the VersionOne along with a link.

Add Member

An Admin User can directly add a user or group of users into VersionOne and can set up username and password on the user or the group’s behalf. It is useful when a team member needs quick access to specific project.

Let us now see the steps to add a team member. The steps are as follows −

To add a single user, click on the Add Member option. It will open a form wherein you have to enter full name, short name, username, password, email address, notification, admin privilege, description, etc. as shown in the screenshot below −

Now, click on Save/Save & New/Save & View button to complete the add process.

Save & New − It will add the user and open a new form to add another user.
Save & View − It will add the user and open the details of the added user.

VersionOne - Add a Project

In this chapter, we will see how to add a project in VersionOne.

Project is the backbone of a Project Management tool. Project represents a set of items and tasks that should be completed in a defined time to consider it as completed. Until a project finds its existence, none of other functionalities/tasks can be performed. Project groups all sprints/backlogs/tasks/issues etc. into one place. In this chapter, we will discuss about adding a project into VersionOne.

To add a project, a user should have the System Admin role.

Create a Project

Project helps to maintain hierarchy of all sub-items like backlog, defects and issues in order to complete it in the defined time. These are useful to centralize multiple backlog as well as relationship with project. In this section, we will discuss the steps performed to add a project into VersionOne. The steps are as follows

Login as Admin and Go to the Settings, present at right top,and select Project & Field Admin → Project as shown in below screenshot. It opens the Project page and displays all available projects in the hierarchy. It will not display any project in case none of the project is added before.

Expand the System (All Projects). Click on the Add Child Project button next to the parent project under which user wants to create the new project as shown below −

It opens the add project form where a user needs to enter the details in the different fields −

Field	Action	Description
Title	Type the name of the project.	The name of the project/release as it displays in the Project Tree.
Parent Project	This field is pre-populated with the name of the parent project. Click on the name to view additional details.	The name of the project that is one level higher in the Project Tree hierarchy.
Iteration Schedule	Click on the magnifying glass to assign an Iteration Schedule to the project.	The Iteration Schedule assigned to the project..
Planning Level	Select one of the following − Enterprise Portfolio Value Stream Release Train Program Increment	Indicates how the specific node is being used in the Project. When this attribute is set on a Project, any new child project will automatically be assigned the next value from the list.
Description	Type a narrative description of the project	This is a rich text field that allows to add expanded details about the project.
Budget	Type in the budget amount	The allocated budget amount for the project/release.
Begin Date	The date the project begins.	The date the project begins. This field is required.
End Date	The date the project ends.	The date the project ends. This field is optional.
Status	Select the status of the project.	Indicates the status of the project.
Owner	Type the first three characters of the project owner's name.	The person to contact if any questions.
Target Swag	Type in the Swag amount.	The amount of Swag user expects to be delivered in the project. Useful when planning.
Target Estimate Points	Type in the Target Estimate amount.	The amount of Estimate you expect to be delivered in the Project. Useful when planning.
Test Suite	Select a TestSuite from the dropdown list.	The TestSuite assigned to the project.
Pipelines	Select a Pipeline from the dropdown list.	Pipelines assigned to the project.
Reference	Type any additional project information.	Free form short text field for information about the project.

Now click on Save/Save & New/Save & View as shown the screenshot below −

After clicking on Save, project gets listed as shown in the screenshot below.

There is Move, Edit, Close and Delete button as well to edit project details and delisted to the project.

VersionOne - Portfolio Planner

Portfolio Planning is used to focus on high level planning. It consolidates the Portfolio Planning, Prioritizing, Tracking and Estimating functionalities. In this chapter, we will discuss about Portfolio Tree, Roadmaps, Kanban board and Timeline. Portfolio Tree and Roadmaps are used at Planning phase while Kanban Board and Timeline are used to track the progress.

Points to Note

In this section, we will discuss how to access Portfolio and the different sub-items.

Portfolio consolidates portfolio planning, their tracking, prioritizing and estimating functions.
A user can access Portfolio planning by navigating Portfolio → Planning.
Similarly, tracking and planning rooms can be accessed as shown below −

Portfolio Planning consists of Portfolio Tree, Roadmaps, Budgets and Strategic Themes.
Portfolio Tracking consists of Kanban Board, Project Timeline and Value Stream Board.

Portfolio Tree

Portfolio Tree represents the Portfolio items into hierarchy – High level to Granular level. It is like Parent-child tree where each Portfolio item is situated under parent item. In the hierarchy/tree, the portfolio present at top is the highest level and decrease step by step for the next item present under that. In this section, we will discuss how the portfolio tree works.

The Portfolio Tree (formerly known as the Epic Tree) allows defining and evaluating the functional hierarchy of features.
A user can prioritize the features based on their relative value and high-level cost.
Whenever required, a user can decompose portfolio items into one to many detailed levels of sub-portfolio items and backlog items that can be delivered by the teams.
While the team works at the backlog items, the Portfolio Tree tracks the progress of the portfolio items. The following screenshot displays the Portfolio tree −

To add a new Portfolio hierarchy, user can click on Add Portfolio Item present at right top.
To add a portfolio item into existing hierarchy, click on the Add Child Portfolio Item on the corresponding level, present at the right side of each portfolio as shown below. It opens the Add Portfolio form where user provide details and click on Save.

Roadmaps

Roadmaps provide a flexible way to display important milestones to stakeholders. It is used to set high level target in defined time. In this section, we will discuss the features of Roadmaps and how it works.

Roadmap is used to keep update the team about progress.
It keeps stakeholders in the loop so that they can understand current priorities and timing and track how their needs will be fulfilled over time.
It provides better feedback into the planning cycle with respect to how stakeholder priorities the requirements.
To access the Roadmaps, navigate to Portfolio → Planning → Roadmaps.
It has 2 different layouts − Board and Timeline

The following screenshot displays the Board Layout view −

The following screenshot dispalys the Timeline layout with respect to the start date and the end date −

Kanban Board

Kanban board is one of the important features designed to track the progress of any project. In Agile methodology, a team can track even day to day activities and progress at backlog items in the Kanban board. In this section, we will discuss the different features of Kanban board −

Kanban board is used to visualize, plan and track the progress of the portfolio items and the child items.
It provides a board view with categorization as None, Define, Breakdown, Build, Test and Deploy. Either of the backlog items/portfolio can be categorized among these based on the progress.
To access it, navigate to Portfolio → Tracking → Kanban Board.
By default, each card shows the ID, title, owner (if applicable), and the Swag (high level size estimate). A user can have the basic details of the card by just viewing the Kanban board. By clicking on the card title, they can view the details of the item.
A user can drag and drop a portfolio item card to another place in the same column (to prioritize the ranking) or move it to another column (to update the status).
Click on the down arrow in the top right corner of a card for access to common the actions as follows −
- Edit portfolio item details − It will allow to edit the details of the item.
- View portfolio item dashboards − It will open all the details in the view mode.
- Block portfolio items − It will block the portfolio item and ask the blocking reason. Even a user can link it with blocking issues/defects/dependent story.
- Close portfolio items − It is used to close the item. Later, it can be re-opened if required.
- Watch portfolio items − It is used to add the item in the watch list and get notification if there is any change; the change can be with the status too.

The following screenshot displays the Kanban Board −

Project Timeline

Project Timeline can be accessed as Portfolio → Tracking → Project Timeline. Project Timeline can be used for the following −

Plan and communicate current and future project delivery.
View historical delivery of projects.
To see the next level of detail, priorities, and progress from a single view.
Understand the organizational velocity achieved in delivering previous projects that can be used as a guide in planning future work.
Project Timeline provides graphical view of projects. It displays the scheduling and delivery of work initiatives, features, and sub-features for specific projects.

The following screenshot displays the Project Timeline’s view −

VersionOne - Product Planner

Product Planning is the actual start of the project. In this phase, Product Owner works with backlog items to prioritize, groom and estimate.

In this chapter, we will discuss how to plan the backlog items and how to manage them in the sprint level.

Points to Note

In this section, we will go through some important points that need to be considered in product planning.

Product Planning is the activity where Product Owners identify, organize and groom the Backlog to prepare it. The development/testing/BA team(s) works on this aspect. If planning does not happen properly, sprint works affect the productivity and timeline of project..
It involves managing the backlog items, test sets and defects that define the updates going into the product.
These items form the backlog and are ranked by priority so they can be scheduled into releases/projects and sprints.
Product Planner is divided into two sections – Planning and Input. The Planning section consists of −
- Backlog − It is used for planning and prioritization of Agile backlog in list view.
- Backlog Groups − It provides the hierarchical functional groupings used to segment the backlog.
- Backlog Goals − It provides the measurable targets to drive the project effort into a proper direction.
The input section consists of −
- Requests − These are generated by customers/stakeholders who approve the assets/backlog.
- Issues − It captures roadblocks or dependencies or other issues that affect the project directly or indirectly.
- Regression Tests − These are templates for Acceptance Tests.
- Templates − It is the standard template that is used to configure stories/defects/backlog items.
- Import − It is the standard template that is used to configure stories/defects/backlog items.

VersionOne - Backlog

Backlog is the list of all work items. Stories, Defects, Test sets are part of work items. Stories are primary items in backlog. Work items categorize and define all works to be done for a project and iteration/sprint level.

Access the Backlog Page

In this section, we will learn how to access the Backlog Page.

Backlog page can be accessed by navigating the Product Planner − Planning − Backlog as shown in the screenshot below. It opens the backlog page; the page consists of all available backlog items.

Backlog Page provides a flexible, editable grid of workitems associated with a project and all of its subprojects.
Here, a user can add new workitems, as well as edit, filter, sort, categorize, and prioritize existing items relative to one another.
In the backlog page, a user can see the following fields for each workitem −
- Order − It shows priority of the workitems.
- Title − Name of each workitems.
- ID − It display unique id of workitems.
- Owner − The person who owns the workitem.
- Priority − It shows how prior the backlog item should consider.
- Estimate Pts − It provides the complexity of workitem.
- Project − It displays the associated project name.

The following screenshot displays the Backlog page view −

Add Backlog Item

A user with proper role can add the Backlog Item into a project. Usually issues and defects can be added by all users having access of project. Stories can be added by the product owner. Now, we will discuss how to add a backlog item.

Go to the Backlog page and click on the arrow sign of the Add Backlog Item Inline button.
It provides 2 different options to add each backlog item or defect.
One option is Add Backlog/Defect Inline and the other is Add Backlog Item/Defect as shown in the screenshot below −

When a user selects the Inline option, a new row gets added as 1st row. Here, the mandatory details can be entered directly.
After that, click on the Save button present at the right side to keep the record of entered details as shown in the following screenshot −

Or,

When a user clicks on Add Backlog Item/Defect, a new window opens along with the different fields to enter the details about workitem.
Once the details are entered, a user clicks on the Save/Save & View/Save & New button.

The following screenshot displays the Add Backlog Item/Defect page −

Backlog Goals

The Backlog Goal contains the group of stories or backlog items that provide the direction to the Project Team. It is usually the standard target (short and long term) to measure the direction of the project team. Consider the following important features of the backlog goal −

A Backlog Goal contains group’s backlog workitems that display the progress of the project team.
It is measurable and specifies the direction and priorities of the project team.
It can have many-to-many relationship with workitems.
It allows free association between stories, defects or even portfolio items to Backlog goals.
To access the Backlog Goals, navigate to Product Planner → Planning → Backlog Goals.
To add a Backlog Goal, click on the Add Backlog Goal button present at the top right as shown in the following screenshot −

It opens a Backlog Goal form in new window.
A user enters the details as Title, Project, Team, Planned Business Value, Actual Business Value, Target in Project, Description, Type and Priority.
After that, click on the Save/Save & View/Save & New button as shown in the screenshot below. It saves the Backlog Goal. The goal can be viewed by a user at a later stage of the project to compare standard Vs actual.

There is an option Summary by Project. When user clicks on this button, a new window opens and displays the progress of each project as % of Backlog Goal and % of Project.

The following screenshot displays the Summary by project −

VersionOne - Story

Story represents requirement, additional or change in existing functionality or new features. Stories are units of business values those can be estimated, tested and completed within a defined sprint.

Stories consist of mainly two aspects −

Acceptance criteria of the functionality to define acceptance tests.
All the tasks are required to be completed by the team to deliver the story.

Add a Story

In this section, we will learn how to add a story. Story can be added by the Product Owner. Usually a team member cannot add a story until he has special roles like that of an admin, product owner, team lead, etc. There are many ways to add a story. We will discuss the ways as options below.

After addition, a symbol in green color shows up. The symbol represents a Story.

Option 1

Go to the Product Planner → Backlog.
Click on the Add Backlog Item Inline button present at the top right.
It will quickly add a top row where a user needs to enter the detail and click on the Save button. It adds the story into backlog items as top row.

The following screenshot displays how to add a story inline −

Option 2

Go to Product Planner → Backlog
Click on arrow symbol of Add Backlog Item Inline button present at top right.
Click on Add Backlog Item option.
A new window opens along with different fields to enter details about story.
Once the details are entered, a user clicks on the Save/Save & View/Save & New button. It adds the story into the backlog items and appears based on applied sorting methods.

The following screenshot displays how to add a story detail −

The following screenshot displays the Story Details page −

Option 3

Click on the + icon at the sidebar menu. It opens the Add New options.
Click on the Backlog Item option as shown in the following screenshot.

A new window opens along with the different fields to enter the details about the story.
Once the details are entered, a user clicks on the Save/Save & View/Save & New button to add the story into the backlog item.

Access Story Details

After the addition of story, details can be accessed by any team member having the project access. In this section, we will discuss how to view all the details of the story.

To view the story details, click on Title or ID anywhere it appears in VersionOne. It opens the story details in a new pop up window.
Conversations and Activity Stream are present at the left side of the page.
At the top right, the Action Menu is present.
Relationship Links are present at the top bar.
The main page consists of the story details.

The following screenshot shows the Story Details page −

From the Story Details page, the following high-level tasks can be performed using the tabs at the top right of the grid −

If a user wants to...	Do this...
View or update story details	Click the Details tab.
View the change history for a story	Click the History tab.
View a graphical representation of the story's relationships to other workitems	Click the Visualize tab.
Edit story details	Click on the dropdown to select the Edit tab and later open the Story Edit window. A user can also open this dropdown menu to perform other actions (Plan Story, Add Task, Add Test, Generate Parent Epic, Copy, Sign Me Up, Block, Split, Quick Close, Close and Convert to Defect, Delete, and Watch Story).

Following screenshot shows the tab of high level tasks −

Manage Story Details

At the bottom of the Story Details page, a user can perform the following functions by clicking the Add or Assign buttons. To remove any items, a user can click Remove from the selected story.

If a user wants to...	Do this...
Add a new task	Go to Tasks and click Add Inline.
Add a new test	Go to Tests and click Add Inline.
Assign upstream dependencies from available backlog	Go to Upstream Dependencies and click Assign.
Assign downstream dependencies from available backlog	Go to Downstream Dependencies and click Assign.
Identify (select) issue(s) have been resolved	Go to Issues Resolved and click Assign.
Select an existing issue to assign as a blocking issue	Go to Blocking Issues and click Assign.
Select existing Backlog items that are affected by the defect	Go to Breaks Workitems and click Assign.
Select an existing request	Go to Requests and click Assign.
Select an existing defect that breaks the selected story	Go to Broken By Defects and click Assign.
Designate the most current build(s) affected by the defect	Go to Last Affected Build Runs and click Assign.
Add a newlink remote documentation	Go to Links and click Add..
Add a new fileattachement	Go to Attachments and click Add..

The following screenshot displays how to manage story details −

VersionOne - Edit Story

In this chapter, we will learn how to edit story in VersionOne. Editing a story consists of many actions. With the Edit Story feature, we can modify the details of the story, close it, delete it, add it into the watchlist, block it with issues or defects, convert into defect, etc. In this chapter, we will discuss how to go about editing story details, closing a story and deleting a story.

Edit Story Details

While editing the story details, a user can edit the details of the story including title, priority, estimation and dependencies. The only field that remains unmodified is the unique id of the story; it can never be changed or modified.

There are three ways to edit a story. The ways are described as options below −