On this page, the QA manager or Test Lead will learn how to get started with TestFLO and how to manage its settings.
Let TestFLO know where your requirements are in Project Settings > Requirements tab, otherwise reports related to requirements will be inaccessible.
TestFLO is extremely configurable. Contact your Jira Administrator in case you’d like to:
Below you can review a general flow that you can use with TestFLO:

More information you can find on the General flow of work page.
Learn more about other operations you can perform on the Test Plan on the Test Plan operations page.
If the default workflow of the Test Plan or Test Cases provided by TestFLO does not reflect the way your team works, you can ask your Jira Administrator to modify it. Some QA managers need to prevent Test Cases from being started before the Test Plan is marked as started, others need to make sure the Test Cases are executed strictly in the order defined in the Test Plan. With TestFLO it is possible to configure such restrictions and many more.
The columns in the Test Cases panel can be modified in TestFLO global settings accessible by your Jira Administrator.
Iterations can have meaningful names, f.e. sprint names, date ranges, build numbers, which are later visible in the Test Plan Iterations Report. If you don’t want new iterations to be started by unaware users, we suggest narrowing down the list of people who can start a new iteration. You can do this in Project Settings > Test Management > Permissions tab.
Find out more about Run automated tests operation here.
Reports related to requirements will become visible after filling in Project Settings > Requirements tab.
If you can’t find the answer you need in our documentation, raise a support request.