#Jira client reports read only how to#

#Jira client reports read only how to#

When thinking about how to best integrate your Jira projects with qTest Manager it is best to understand which milestones best drive your testing efforts, Releases or Sprints.įor instructions on how to import Releases and requirements from Jira. Features and issues may change sprints during a Release (or even change releases), and once a team reaches a Release date, any incomplete features may move out of their active Sprints into the product backlog to be reassigned.īecause of this, Releases may span multiple sprints and sprints may span multiple releases. A sprint is a collection of features you ideally will complete in a fixed period of time, but you may not necessarily do so by the Release date. Sprints define a period of time in which development teams implement and deliver a prescribed amount of product functionality. To ensure teams Release new versions on a regular basis, Releases are often scheduled on a fixed date. Assigning issues to versions will determine which new features for your application will be available to your customers when the Release is deployed. Scrum Projects in Jira are recommended for teams working with an iteration-based approach to development.Ī Release (or Fixed Version) is a set of features (issue types) deployed together as a single update to your application being developed. How do you recommend we configure the Release and Requirement integration in qTest Manager? Overview My team uses both Releases AND Sprints in our Jira Scrum Project. Structuring qTest Projects Integrated with Jira Use Case