Share this page

# Analyze development in your SCM system

If your CI server is set up to work with a source control management (SCM) system, you can use the Development tab to track committed changes, branches, and pull requests that are related to your backlog items.

The Development tab includes the following sections.

Area | Description
--- | ---
Commits | Pipelines display the commits associated with each run of the pipeline. You can associate a commit with specific backlog items (user stories, quality stories, or defects), and track committed changes and their affect on release and build quality. For examples, see Use-cases for tracking commits. For details on how to work with commits, see Track commits to your SCM system.
Branches | You can track branches in your SCM system via Jenkins, and get details on their impact on release and build quality. For example, you can see details on branches in the context of a feature and its user stories, and whether it was merged to the master branch. For details, see Track branches in your SCM system.
Pull requests | If your Jenkins server works with a source control management (SCM) system using pull requests, you can track pull requests that are related to your backlog items. For example, if QA wants to verify that a feature is complete, they can check that all pull requests were merged and that there are no open pull requests. For details, see Track pull requests in your SCM system.

### See also

- Set up your SCM system

https://admhelp.microfocus.com Software Delivery Management 8942
Tips to improve your search results... OpenText™ Software Delivery Management Help Center OpenText™ Software Delivery Management Help 26.3 All View Local Help Center View Online Help Center Version: