{% extends "cacsremoteservice/views/layouts/project-view.html" %}

{% block scripts %}
<script type="text/javascript">
  var projectId = {{item.id}};
  var analysisPlan = '{{item.analysisplan}}';
  codescene.views.projects.configuration.init(projectId, analysisPlan);
  {% for badge in item.status-badges %}
  {% if not badge.non-architectural-message %}
      codescene.views.configurations.statusBadgeExample.init(
        $('#{{badge.identifier|name}}-granular-badges-container')[0], {
          itemId: {{item.id}},
          badge: {{badge|json|safe}},
          archComponents: {{item.arch-components|json|safe}}
        }
      );
    {% endif %}
  {% endfor %}
</script>
{% endblock %}

{% block main-container %}
<div id="side-nav-bar+content+footer" class="flex-column h-92vh">
  {% include "cacsremoteservice/views/projects/project-header.html" with project=item tabs=tabs %}
  {% include "cacsremoteservice/views/partials/validation-errors.html" %}
  <form action="" method="post" id="configform" enctype="multipart/form-data" class="project-configuration-view">
    <aside class="aside-nav">
      <ul class="nav nav-pills nav-stacked">
        <li data-tab-id="general"><a href="#general">General</a></li>
        <li data-tab-id="social-network"><a data-automation-id="teams-developers-configuration" href="#social-network">Teams/Developers</a></li>
        <li data-tab-id="analysis-plan"><a href="#analysis-plan">Analysis Plan</a></li>
        <li data-tab-id="exclusions-and-filters"><a href="#exclusions-and-filters">Exclusions &amp; Filters</a></li>
        <li data-tab-id="codehealth"><a href="#codehealth">Code Health</a></li>
        <li data-tab-id="ticket-id-mapping"><a href="#ticket-id-mapping">Ticket ID Mapping</a></li>
        <li data-tab-id="temporal-coupling"><a href="#temporal-coupling">Change Coupling</a></li>
        <li data-tab-id="code-churn"><a href="#code-churn">Code Churn</a></li>
        <li data-tab-id="architecture"><a href="#architecture" data-automation-id="architectural-components-link">Architecture</a></li>
        <li data-tab-id="status-badges"><a href="#status-badges">Status badges</a></li>
        <li data-tab-id="branches"><a href="#branches">Branches, Risks &amp; Process</a></li>
        <li data-tab-id="delta-analysis"><a href="#delta-analysis">Delta Analysis</a></li>
        <li data-tab-id="delivery-performance"><a href="#delivery-performance">Delivery Performance</a></li>
      </ul>
    </aside>
    <div id="page-body" class="configuration-tabs">
      <div class="tab-content">
        <input type="hidden" name="startdate" value="{{item.start-date}}"/>
        <div class="tab active" data-tab-id="general">
          <h2>General</h2>
          <div class="form-group">
            <label>Name</label>
            <input class="form-control" type="text" name="name" value="{{item.name}}" required/>
          </div>
          
          {% if item.project-groups|not-empty %}
            <div class="form-group">
              <label for="group-id">Project Group</label>
              <select class="form-control"
                      id="group-id"
                      name="group-id"
                      required>
                {% for group in item.project-groups %}
                  <option value="{{group.id}}"
                    {% ifequal item.group-id|default:default-group group.id %} selected{% endifequal %}>
                  {{group.name}}
                  </option>
                {% endfor %}
              </select>
            </div>
          {% endif %}

          <div class="form-group">
            <label>Analysis Project Owner</label>
            <input class="form-control" type="text" name="project_owner" value="{{item.project_owner}}" />
            <span class="help-block">Specify a point of contact for this analysis project, e.g. name or email (free text field).</span>
          </div>

          <div class="form-group">
            <label>Description</label>
            <input class="form-control" type="text" name="description" value="{{item.description}}" />
            <span class="help-block">A free text field where you can add notes describing your configuration.</span>
          </div>

          {% ifunequal item.local-path-for-remotes "" %}
          <div class="form-group">
            <input type="hidden" name="fixed_repo_roots" value="{{item.fixed_repo_roots}}" />
            <label>Local Path to the Directory where CodeScene will clone your Remotes</label>
	    
            <input class="form-control"
                   {% if not item.is-admin %}
                   {% if item.fixed_repo_roots %}
                   readonly
                   {% endif %}
                   {% endif %}
                   type="text"
                   name="local-path-for-remotes" value="{{item.local-path-for-remotes}}" />
            {% if item.fixed_repo_roots %}
            <span class="help-block">This path is auto generated from your admin settings, and points to a folder where the remotes will be cloned.</span>
            {% else %}
            <span class="help-block">A path to a writeable folder where we'll clone your remotes. If you change the path we'll re-clone each Git remote.</span>
            {% endif %}
          </div>
          {% endifunequal %}

	  
          <div class="form-group">
	          <div class="row">
	            <div class="col-md-7">
                <label>Repository</label>
	            </div>
	          <div class="col-md-3">
		          <label>Ref</label>
	          </div>
	        </div>
	    
          <div class="input-list" id="repository-path-list">
            {% for vcs in item.repo-paths %}
	          <div class="row repository-row">
		          <div class="col-md-7 repo-path">
		            <input class="repo-path-input form-control col-md-7"
                  type="text" name="vcs_{{forloop.counter}}"
                  placeholder="Enter another repository path..."
                  value="{{vcs.path}}" />
                <div class="col-md-8 repo-path-alert"></div>
		          </div>
		          <div class="col-md-3 repo-ref {{vcs.validity}}">
                <select class="repo-ref-specific" name="vcs_branch_{{forloop.counter}}">
                  <option value="{{vcs.branch}}" selected>{{vcs.branch}}</option>
                  {% for b in vcs.other-branches %}
                  <option value="{{b}}">{{b}}</option>
                  {% endfor %}
                </select>
		          </div>
            </div>
            {% endfor %}
	          <div class="row">
              <div class="col-md-7">
                <input class="repo-path-input form-control col-md-8"
                  type="text"
                  name="vcs_{{vcss|count}}"
                  placeholder="Enter another repository path..."
                  value="" />
                <div class="col-md-8 repo-path-alert"></div>
              </div>
	          </div>
          </div>
          <span class="help-block">The paths to your version-control directories.</span>
        </div>

          <div class="form-group">
            <input type="hidden" name="fixed_results_root" value="{{item.fixed_results_root}}" />
            <label>Analysis results</label>
            <input class="form-control"
                   type="text"
                   {% if not item.is-admin %}
                   {% if item.fixed_results_root %}
                   readonly
                   {% endif %}
                   {% endif %}
                   name="results"
                   value="{{item.analysis-path}}"
                   required/>
            {% if item.fixed_results_root %}
            <span class="help-block" id="analysis-destination-help-block">
              This path is auto generated from your admin settings. It specifies a folder where the analysis results will
              be written. This would, typically, be a persistent folder.
            </span>
            {% else %}
            <span class="help-block" id="analysis-destination-help-block">
              A path to a (writeable) folder for analysis results. <strong>Must
                be a directory outside of the repositories you analyze.</strong>
            </span>
            {% endif %}
          </div>
          <div class="form-group">
            <label>Include history from</label>
            <input class="form-control" type="date" name="firstanalysisdate" value="{{item.analysis-start-date}}"/>
            <span class="help-block">Specifies how far back in time we will go to collect data. Leave empty for the largest possible range.</span>
          </div>
          <div class="form-group sliding-window">
            <label>Hotspot analysis time span (sliding window)</label>
            <select  name="technical-analysis-span-option" id="technical-analysis-span-option">
              <option value="{{item.hotspots-sliding-window-time}}" selected>{{item.hotspots-sliding-window-time}}</option>
              {% for b in item.technical-span-options %}
              <option value="{{b}}">{{b}}</option>
              {% endfor %}
            </select>
            <span class="help-block">
              Specifies how far back in time to collect Hotspot
              data. When the full history is used, the results will be
              more complete but might include hotspots that have
              recently become stable. This option does not affect any
              other analysis time frames.
            </span>
          </div>
          <div class="form-group sliding-window">
            <label>Cost analysis time span (sliding window)</label>
            <select  name="pm-data-analysis-span-option" id="pm-data-analysis-span-option">
              <option value="{{item.pm-data-sliding-window-time}}" selected>{{item.pm-data-sliding-window-time}}</option>
              {% for b in item.pm-data-span-options %}
              <option value="{{b}}">{{b}}</option>
              {% endfor %}
            </select>
            <span class="help-block">
              Specifies how far back in time to collect Cost and Cost trends from
              a project/lifecycle tool integration (e.g. Jira, GitHub Issues, Azure DevOps).
            </span>
          </div>
          <div class="form-group sliding-window">
            <label>Team analysis time span (sliding window)</label>
            <select  name="team-analysis-span-option" id="team-analysis-span-option">
              <option value="{{item.team-analysis-sliding-window-time}}" selected>{{item.team-analysis-sliding-window-time}}</option>
              {% for b in item.team-analysis-span-options %}
              <option value="{{b}}">{{b}}</option>
              {% endfor %}
            </select>
            <span class="help-block">
              Specifies how far back in time to analyse team work (coordination, team coupling, etc.). This should
              typically be a short time span since teams tend to be more volatile than code, and you want the
              analyses to reflect recent acitivity, not old team contribution patterns.
              If the <strong>Full</strong> option is selected, CodeScene will use the starting date specified
              below for Start team analyses.
            </span>
          </div>
          <div class="form-group">
            <label>Start team analyses from</label>
            <input class="form-control" type="date" name="team-analysis-start-date" value="{{item.team-analysis-start-date}}"
                   required/>
            <span class="help-block">This is used as the start date for team analyses in case the <strong>Full</strong> option
              is specified above.
            </span>
          </div>
          <div class="form-group">
            <label>
              <input type="checkbox" name="complete-history-for-social" value="complete-history-for-social" {% if item.complete-history-for-social %} checked {% endif %}/>
              Use the complete Git history for knowledge metrics
            </label>
            <span class="help-block">When checked, we use the complete Git history to calculate individual knowledge metrics independent of your analysis period. Uncheck if you want a faster analysis and don't care about individual metrics.</span>
          </div>
          <div class="form-group">
            <label>
              <input type="checkbox"
		            name="update-repositories"
		            value="update-repositories"
		            {% if item.update-repositories %} checked="" {% endif %}/>
              Update repositories before analysis
            </label>
            <span class="help-block">
	          Pulls the latest changes before each analysis. Uncheck if updating repositories is not possible.
	          </span>
          </div>
          <div class="form-group">
            <label>
              <input type="checkbox" name="lookup-copied-content" value="lookup-copied-content" {% ifequal item.lookup-copied-content 1 %}checked="" {% endifequal %}/>
              Look up initial file size for content copied from other files
            </label>
            <span class="help-block">
              By checking this box you improve the accuracy of the knowledge metrics in case you have content that's frequently extracted/copied from other files. The disadvantage is that this operation may slow down the analysis on large projects.
            </span>
          </div>
          <div class="form-group">
            <label>
              <input type="checkbox" name="cache-vcs-data" value="cache-vcs-data" {% if item.cache-vcs-data %}checked="" {% endif %}/>
              Cache VCS data
            </label>
            <span class="help-block">
              If enabled, VCS data will be stored and reused in subsequent analysis improving performance.
            </span>
          </div>
          <div class="form-group">
            <label>
              <input type="checkbox" name="cache-scoring-data" value="cache-scoring-data" {% if item.cache-scoring-data %}checked="" {% endif %}/>
              Cache Code Health Score data
            </label>
            <span class="help-block">
              If enabled, Code Health Score data will be stored and reused in subsequent analysis improving performance.
            </span>
          </div>

        </div>

        <div class="tab" data-tab-id="social-network">
          {% include "cacsremoteservice/views/projects/configuration/social.html" %}
        </div>

        <div class="tab" data-tab-id="analysis-plan">
          <h2>Analysis Plan</h2>
          <p class="lead text-muted">
            You need to specify how frequently the analysis shall run. Our
            recommendation is to run the analysis once every night on an active
            development project and once a week on stable maintenance projects.
          </p>
          <div style="display: flex; gap: 6px;">
            <div id="analysisplan"></div>
            <span><b>{{ server-timezone }}</b></span>
          </div>

          <h3>Analysis House-Keeping</h3>
          <p class="lead text-muted">
            CodeScene cleans out old analysis results for you to save disk space.
          </p>
          <div class="form-group">
            <label>
              <input type="checkbox" name="do_housekeeping" value="do_housekeeping" {% ifequal item.do_housekeeping "1" %} checked="" {% endifequal %}/>
              Auto-delete old analysis results
            </label>
            <span class="help-block">Enable to let CodeScene do the house-keeping.</span>
          </div>
          <div class="form-group">
            <label>Historic Analyses to keep</label>
            <input class="form-control" type="number" name="max_history_depth" value="{{item.max_history_depth}}" required min="1" 
                   {% ifunequal item.do_housekeeping "1" %} disabled="" {% endifunequal %} />
            <span class="help-block">Just keep this number of historic analyses, delete older ones.</span>
          </div>
          <div class="form-group">
            <label>Max age of analysis results (weeks)</label>
            <input class="form-control" type="max_historic_age" name="max_historic_age" value="{{item.max_historic_age}}" required min="1"
                   {% ifunequal item.do_housekeeping "1" %} disabled="" {% endifunequal %} />
            <span class="help-block">Auto-delete analysis results that are older than the specified number of weeks.</span>
          </div>
        </div>
        <div class="tab" data-tab-id="exclusions-and-filters">
          <h2>Exclusions &amp; Filters</h2>
          <section>
            <h3>General exclusions</h3>
            <div class="form-group">
              <label>Exclude files</label>
              <datalist id="patterns">
                <option value="{{item.exclusionfilter}}">
                <option value="*.sln;*.csproj;*.resx;*.vbproj;*.xproj;*.xml;*.md;*.txt">
                <option value="*.xml;*.json;*.md;*.txt;*.gradle">
              </datalist>
              <input class="form-control" type="text" list="patterns" name="exclusionfilter" value="{{item.exclusionfilter}}" />
              <span class="help-block">A semicolon-separated list of file extensions (see <a
                                                                                            href="{{view-context}}/docs/configuration/projects.html#exclude-files-from-an-analysis" target="_blank">docs</a>)</span>
            </div>
            <div class="form-group">
              <label>Exclude content</label>
              <input class="form-control" type="text" name="excludecontent" value="{{item.excludecontent}}" placeholder="repository-root-folder/glob pattern"/>
              <span class="help-block">A semicolon-separated list of <a href="{{view-context}}/docs/configuration/projects.html#a-brief-guide-to-glob-patterns" target="_blank">glob patterns</a> for content you want to exclude (see <a
                                                                                                                                                                                                                                         href="{{view-context}}/docs/configuration/projects.html#exclude-specific-files-and-folders-from-an-analysis" target="_blank">docs</a>)</span>
            </div>
            <div class="form-group">
              <label>White List content</label>
              <input class="form-control" type="text" name="whitelistcontent" value="{{item.whitelistcontent}}" placeholder="repository-root-folder/glob pattern"/>
              <span class="help-block">Specify a semicolon-separated list of <a href="{{view-context}}/docs/configuration/projects.html#a-brief-guide-to-glob-patterns" target="_blank">glob patterns</a> for content you want to include. White listed content is applied before the exclusion patterns above (see <a
                                                                                                                                                                                                                                                                                                                      href="{{view-context}}/docs/configuration/projects.html#exclude-specific-files-and-folders-from-an-analysis" target="_blank">docs</a>)</span>
            </div>
            <div class="form-group">
              <label>Exclude commits</label>
              <input class="form-control" type="text" name="excludecommithashes" value="{{item.excludecommithashes}}" placeholder="05226a4a55bbccd6aacd01491a4026e9c132db38"/>
              <span class="help-block">Exclude commits that represent an initial import of the whole codebase. Semicolon-separated list of Git commit hashes</span>
            </div>
            <div class="form-group">
              <label>
                <input type="checkbox" name="selectdistinctcommits" value="selectdistinctcommits" {% ifequal item.selectdistinctcommits 1 %}checked="" {% endifequal %}/>
                Select distinct commits
              </label>
              <span class="help-block">
                Automatic imports from other version-control systems to Git, e.g.
                <em>git-tfs</em>, can produce duplicate commits. With this
                option enabled the analysis engine tries to remove all such
                duplicates.
              </span>
            </div>
            <div class="form-group">
              <label>
                <input type="checkbox" name="auto-detect-text-files" value="auto-detect-text-files" {% ifequal item.auto-detect-text-files 1 %}checked="" {% endifequal %}/>
                Detect all files with text content
              </label>
              <span class="help-block">
                Check this box to have CodeScene include all text content from your codebase in the analysis. This lets you include programming languages that CodeScene doesn't have native support for. The drawback is potentially longer analysis times. Text content is detected by each file's <em>MIME</em> type.
              </span>
            </div>
          </section>
          {% if feature-flags.code-coverage? %}
          <section>
            <h3>Code Coverage exclusions</h3>
            <p>Exclude selected files and folders from the code coverage analytics.</p>
            <p>
              By default, files for which no code coverage data is available are considered to have 0% coverage and are displayed as red in the system map.
              This also affects the calculation of the code coverage KPIs.
            </p>
            <p>
              To avoid these false positives, you can provide glob patterns that match the files you wish to exclude from the code coverage analysis.
              Glob patterns must begin with the repository root.
              Consult the <a href="{{view-context}}/docs/integrations/setting-up-code-coverage.html#excluding-false-positives-from-the-code-coverage-analysis">documentation</a> for more details.
            </p>
            
            <div class="form-group">
              <label>Exclude paths from code coverage</label>
              <input type="text" class="form-control"
                     name="code-coverage-exclusions-content"
                     value="{{item.code-coverage-exclusions-content}}"
                     placeholder="repo/config-files/**"/>
              <span class="help-block">A semicolon-separated list of  <a href="{{view-context}}/docs/configuration/projects.html#a-brief-guide-to-glob-patterns" target="_blank">glob patterns</a> that begin with the repository root for that path.</span>
            </div>
          </section>
          {% endif %}
        </div>

        <div class="tab" data-tab-id="codehealth">
          {% include "cacsremoteservice/views/projects/configuration/codehealth.html" %}
        </div>

        <div class="tab" data-tab-id="ticket-id-mapping">
          <h2>Ticket ID Mapping</h2>
          <p class="lead text-muted">
            By specifying a Ticket ID pattern, individual commits can be linked to tickets, allowing for
            measuring Change Coupling Across Commits and Code Churn by Tasks. individual commits can be linked to tickets, allowing for measuring change coupling across commits.
            <br><br>
            If PM Data Integration is enabled, the pattern used for matching will be created automatically
            to extract ticket IDs matching the configured integration.
            </p>
          </p>
          <div class="form-group">
            <label>Ticket ID Pattern</label>
            <input class="form-control" type="text" name="ticketidpattern"
                   {% if item.pm-data-enabled %}readonly{% endif %}
                   value="{{item.ticketidpattern}}" placeholder="Example: MYPROJ-(\d+)" />
            <span class="help-block">
              A regular expression with exactly one
              (1) group. The pattern extracts a Ticket ID from your commit
              messages. For example, <code>([A-Z]{2,}-\d+)</code> matches
              tickets like ARB-782 and BI-231, while the expression
              <code>#(\d+)</code> matches GitHub's issue numbers.
            </span>
          </div>

          <div class="form-group">
            <label for="ticket-id-uri-template">Ticket URI Template</label>
            <input class="form-control"
                   {% if item.pm-data-enabled %}disabled{% endif %}
                   type="text"
                   name="ticket-id-uri-template"
                   id="ticket-id-uri-template"
                   value="{{item.ticket-id-uri-template}}"
                   placeholder="https://your-ticket-uri.example.com/tickets/{ticket-id}" />
            <div class="help-block">
              A URI template, with a single <code>{ticket-id}</code> expression for
              the ticket ID value, that will be used to hyperlink to your
              ticket system in analysis result views.
              <code>https://github.com/owner/name/issues/{ticket-id}</code>
              links the above mentioned Ticket ID pattern to a GitHub
              issue tracker for the <em>owner/name</em> repository. Learn
              more in <a
                        href="{{view-context}}/docs/configuration/projects.html#linking-to-an-external-ticket-system">the
                documentation</a>.
            </div>
          </div>

        </div>
        <div class="tab" data-tab-id="temporal-coupling">
          <h2>Change coupling</h2>
          <section>
            <h3>By Commits</h3>

            <div class="form-group">
              <label>Minimum revisions</label>
              <input class="form-control" type="number" name="minrevs" value="{{item.minrevs}}" required min="2" />
              <span class="help-block">Exclude files with fewer revisions from the coupling analyses.</span>
            </div>

            <div class="form-group">
              <label>Max changeset size to include</label>
              <input class="form-control"
                     type="number"
                     name="maxchangesetsize"
                     value="{{item.maxchangesetsize}}"
                     min="10"
                     max="1000"
                     step="10"
                     required/>
              <span class="help-block">Excludes commits with more files than your given value in order to ignore accidental coupling.</span>
            </div>
          </section>

          <section>
            <h3>By Logical Changesets</h3>
            <div class="form-group">
              <label>
                <input type="radio"
                       name="temporal-coupling-strategy"
                       id='couplingbytime'
                       value="by-time"
                       {% ifequal item.temporal-coupling-strategy-str "by-time" %} checked="checked" {% endifequal %} />
                By Author and Time
              </label>
              <label>
                <input type="radio"
                       name="temporal-coupling-strategy"
                       id='couplingbyticket'
                       value="by-ticket-id"
                       {% ifequal item.ticketidpattern "" %} disabled="disabled" {% endifequal %}
                       {% ifequal item.temporal-coupling-strategy-str "by-ticket-id" %} checked="checked" {% endifequal %} />
                By custom Ticket ID
              </label>
              <span class="help-block">Specify how you want to measure temporal coupling across multiple projects or across individual commits (learn more in <a
                                                                                                                                                                href="{{view-context}}/docs/configuration/projects.html#measure-temporal-coupling-across-multiple-projects" target="_blank">the documentation</a>).
                The option "By custom Ticket ID" requires <a href="#ticket-id-mapping">Ticket ID Mapping</a> configuration.
              </span>
            </div>
            <div class="form-group">
              <label>Max changeset size to include</label>
              <input class="form-control"
                     type="number"
                     name="temporal_coupling_across_maxchangesetsize"
                     value="{{item.temporal_coupling_across_maxchangesetsize}}"
                     min="10"
                     max="1000"
                     step="10"
                     required/>
              <span class="help-block">Excludes commits with more files than your given value in order to ignore accidental coupling.</span>
            </div>
            <h4>File Level</h4>
            <div class="form-group">
              <label>Minimum co-occurrence</label>
              <input class="form-control" type="number" name="temporal_coupling_across_minrevs" value="{{item.temporal_coupling_across_minrevs}}" required min="2" />
              <span class="help-block">Exclude files with fewer revisions or common Ticket IDs from the coupling analyses.</span>
            </div>
            <h4>Architectural Level between Logical Components</h4>
            <div class="form-group">
              <label>Minimum co-occurrence</label>
              <input class="form-control" type="number" name="temporal_coupling_archlevel_across_minrevs" value="{{item.temporal_coupling_archlevel_across_minrevs}}" required min="2" />
              <span class="help-block">Exclude components with fewer revisions or common Ticket IDs from the coupling analyses.</span>
            </div>
          </section>

          <section>
            <h3>Change Coupling Filters</h3>

            <p class="text-muted">
              Add filters to exclude change couplings by default, for
              example files that you expect to change together. See
              <a href="{{view-context}}/docs/configuration/projects.html#change-coupling-exclusion-filters">
                the documentation</a> for more details and examples.
            </p>

            <div class="form-group">
              
              <table class="table table-narrow">
                <thead>
                  <tr>
                    <th>Filter Name</th>
                    <th>Pattern (File 1)</th>
                    <th>Pattern (File 2)</th>
                    <th class="column-actions"></th>
                  </tr>
                </thead>
                
                <tbody>
                  {% for filter in item.temporal-coupling-filters %}
                  <tr>
                    <td>
                      <input type="text"
                             name="temporal-coupling-filters[{{forloop.counter0}}][name]"
                             value="{{filter.name}}"
                             class="form-control">
                    </td>
                    <td>
                      <input type="text"
                             name="temporal-coupling-filters[{{forloop.counter0}}][pattern-1]"
                             value="{{filter.pattern-1}}"
                             class="form-control">
                    </td>
                    <td>
                      <input type="text"
                             name="temporal-coupling-filters[{{forloop.counter0}}][pattern-2]"
                             value="{{filter.pattern-2}}"
                             class="form-control">
                    </td>
                    <td class="column-actions">
                      <button class="default-button danger icon clear-temporal-coupling-filter">
                        <i class="fa fa-trash"></i>
                      </button>
                    </td>
                  </tr>
                  {% endfor %}
                </tbody>
                <tfoot>
                  <tr>
                    <td>
                      <input type="text"
                             name="temporal-coupling-filters[{{item.temporal-coupling-filters|count}}][name]"
                             placeholder="New filter name..."
                             class="form-control">
                    </td>
                    <td>
                      <input type="text"
                             name="temporal-coupling-filters[{{item.temporal-coupling-filters|count}}][pattern-1]"
                             class="form-control">
                    </td>
                    <td>
                      <input type="text"
                             name="temporal-coupling-filters[{{item.temporal-coupling-filters|count}}][pattern-2]"
                             class="form-control">
                    </td>
                    <td></td>
                  </tr>
                </tfoot>
              </table>
            </div>
          </section>
        </div>

        <div class="tab" data-tab-id="code-churn">
          <h2>Code Churn</h2>

          <div class="form-group">
            <label>Rolling average (days)</label>
            <input class="form-control" type="number" name="rollingaveragedays" value="{{item.rollingaveragedays}}" required min="7" />
            <span class="help-block">The number of days used to calculate a rolling average of your churn.</span>
          </div>

        </div>

        <div class="tab" data-tab-id="architecture" id="architecture">
          <div class="row">
            <div class="col-xs-12">
              <h2>Architecture</h2>
              <h3>Architectural Components</h3>
              <p>
                Specify the logical components in your codebase. The definitions are used for the architectural analyses (see <a
                                                                                                                                href="{{view-context}}/docs/guides/architectural/architectural-analyses.html#define-your-architectural-components">
                  the documentation
                </a> for examples).
              </p>
            </div>
          </div>
          <div class="row">
            <div class="col-xs-12">
              <a class="default-button"
	         id="goto-architectural-component-editor"
	         href="architectural-components"
           data-automation-id="architectural-editor">
	        Architectural Component Editor
              </a>
            </div>
          </div>
          {% if feature-flags.ranked-architectural-components %}
          <hr/>
          <div class="form-group">
            <h4>Enable manual match priority for architectural components</h4>
            <p>BETA: Allows fine-grained nesting of architectural component patterns by controlling the order in which files are matched to components.</p>
            <label>
              <input type="checkbox" name="enable-architectural-match-priority" value="enable-architectural-match-priority" {% if item.enable-architectural-match-priority %}checked="" {% endif %}/>
              Enable match priority of architectural components
            </label>
          </div>
          {% endif %}
          <div class="row">
            <div class="col-xs-12">
              <hr />
              <h4>Import/Export Architectural Definitions</h4>
              <p>
                Instead of specifying the patterns manually in the section above, you can import a CSV file with the definitions. This is a simpler option in a large system where you can script the generation of the CSV to import.
              </p>

              <p>
                The CSV file must have two columns, without any header row:
              </p>

              <ol>
                <li>Component Name</li>
                <li>Glob Pattern</li>
              </ol>

              <p>
                See
                <a href="{{view-context}}/docs/guides/architectural/architectural-analyses.html#import-architectural-component-definitions-from-a-file">
                  the documentation</a> for more details.
              </p>

              <div class="form-group">
                <input class="form-control" type="file" accept=".csv" name="importarchfile"/>
                <span class="help-block">
                </span>
              </div>
              <p>
                <i class="fa fa-warning text-warning"></i>
                Any import will overwrite existing architectural definitions.
              </p>
              <a class="default-button" id="export-architectural-components" href="export/architectural-components.csv">
                Export Architectural Definitions
              </a>
            </div>
          </div>

          <div class="row">
            <div class="col-xs-12">
              <h3>Architectural Trends</h3>
              <p class="lead text-muted">Complexity trends on the architectural level.</p>
              <p><em>
                <strong>Deprecation warning:</strong>
                The architectural trends are deprecated and will be removed in the future. This information is better captured by other KPIs.
              </em></p>
              <p>
                CodeScene is able to calculate complexity trends on an architectural level (see <a
                                                                                                  href="{{view-context}}/docs/guides/architectural/architectural-analyses.html#system-complexity-trend">
                  the documentation
                </a> for examples). However, this feature is expensive in
                terms of analysis time. You toggle the feature on and off here.
              </p>
            </div>
          </div>
          <div class="form-group">
            <label>System Level Complexity Trend</label>
            <div class="radio">
              <label>
                <input type="radio" name="systemleveltrend" value="1" {% ifequal item.systemleveltrend "1" %} checked="" {% endifequal %} />
                Disabled
              </label>
            </div>
            <div class="radio">
              <label>
                <input type="radio" name="systemleveltrend" value="2" {% ifequal item.systemleveltrend "2" %} checked="" {% endifequal %}/>
                Enabled
              </label>
            </div>
            <span class="help-block">
              Specify if you want CodeScene to calculate an aggregated complexity trend on your overall codebase.
            </span>
          </div>
        </div>

        <div class="tab" data-tab-id="status-badges">
          <h3>Status Badges</h3>
          <p>
            Status badges help stakeholders stay up to date on the health of
            your project. They can be embedded anywhere, as long as CodeScene is
            available on the same network.
          </p>

          <p>
             When you select a badge below, you'll see HTML and
             Markdown code you can use for embedding badges. 
          </p>

          <p>
            <strong>Security:</strong> status badges
            are <strong>public</strong>. When activated here, the badge image
            itself is visible to anyone with access to the same
            network. Activating a badge does not open any other access besides
            the image itself.
          </p>

          <div class="status-badge-selector">
              {% for badge in item.status-badges %}
              {% if badge.identifier %}
              <div class="status-badge">
                  <div class="badge-and-label">
                      <input name="authorized-status-badges"
                             value="{{ badge.identifier|name }}"
                             id="status-badge-{{ badge.identifier|name }}"
                             type="checkbox" {% if badge.authorized %}checked{% endif %}
                             />
                      <label class="badge-title" for="status-badge-{{ badge.identifier|name }}">{{ badge.display }}</label>
                      <img src="{{ view-context }}/imgs/{{ badge.identifier|name }}-example.svg"/>
                  </div>
                  <div class="examples-container {% if badge.authorized %}selected{% else %}not-selected{% endif %}">
                    <div class="markdown ">
                      <div class="markup-label">Markdown</div>
                      <pre>[![CodeScene {{ badge.display }}](CS_URL/{{ item.id }}/status-badges/{{ badge.identifier|name }})](CS_URL/{{ item.id}}/analyses/latest)</pre>
                    </div>
                    <div class="html">
                      <div class="markup-label">HTML</div>
                      <pre>&lt;a href="CS_URL/{{ item.id }}/analyses/latest"&gt;
  &lt;img src="CS_URL/{{ item.id }}/status-badges/{{ badge.identifier|name }}"&gt;
&lt;/a&gt;</pre>
                    </div>
                  </div>

                  <div class="examples-container {% if badge.authorized %}selected{% else %}not-selected{% endif %}">
                  {% comment %} See https://trello.com/c/qcfqrCto/794-provide-missed-goals-badge-on-architectural-component-level {% endcomment %}
                  {% if badge.non-architectural-message %}
                    <div><strong>Note:</strong> {{ badge.non-architectural-message }}</div>
                  {% else %}
                    <div id="{{badge.identifier|name}}-granular-badges-container"></div>
                  {% endif %}
                  </div>
              </div>
              {% endif %}
              {% endfor %}
          </div>

          <div class="analyzed-by-codescene">
            <h3>Static badge for remote use</h3>
            <img src="{{ view-context }}/imgs/analyzed-by-codescene-badge.svg" width="250"/>
            <p>
              If your code is hosted on GitHub and CodeScene is on
              your local network, status badges will not work as
              expected. GitHub serves externally hosted images through
              a proxy server which requires direct access to the image
              source. 
            </p>
            <p>
              In these cases, the next best solution is to display a
              static badge. The image is hosted
              at <a href="https://codescene.com/status/analyzed-by-codescene-badge.svg">codescene.com</a> or you
              can copy it to your own server. When used with the
              markup provided here, it will still allow your users to
              quickly navigate to their project on CodeScene.
            </p>
            <div class="status-badge">
              <div class="examples-container">
                <div class="markdown">
                  <div class="markup-label">Markdown</div>
                  <pre>[![CodeScene {{ badge.display }}](https://codescene.com/status/analyzed-by-codescene-badge.svg)](CS_URL/{{ item.id}}/analyses/latest)</pre>
                </div>
                <div class="html">
                  <div class="markup-label">HTML</div>
                  <pre>&lt;a href="CS_URL/{{ item.id }}/analyses/latest"&gt;
    &lt;img src="https://codescene.com/status/analyzed-by-codescene-badge.svg"&gt;
  &lt;/a&gt;</pre>
                </div>
              </div>
            </div>
          </div>

          
        </div>


        <div class="tab" data-tab-id="branches">
          <h2>Branch Analyses &amp; CI/CD Process</h2>
          <div class="form-group">
            <label>
              <input type="checkbox" name="calculate-branch-statistics" value="calculate-branch-statistics" {% if item.calculate-branch-statistics %}checked="" {% endif %}/>
              Enable branch analyses
            </label>
            <span class="help-block">Measures lead times, developer congestion, and delivery risks on feature branches. Enabling this option may add to the overall analysis duration.</span>
          </div>
          <div class="form-group">
            <label>Age of an active branch (weeks)</label>
            <input class="form-control" type="number" name="branches-analysis-lookback-weeks" value="{{item.branches-analysis-lookback-weeks}}" required min="1"
                   {% if not item.calculate-branch-statistics %} disabled="" {% endif %} />
            <span class="help-block">Defines the maximum age of an active branch. Branches that have been modified within this number of weeks are considered active and included in the analysis.</span>
          </div>
          <div class="form-group">
            <label>Exclude branches</label>
            <input class="form-control" type="text" name="branch-name-exclusion-pattern" value="{{item.branch-name-exclusion-pattern}}"
                   {% if not item.calculate-branch-statistics %} disabled="" {% endif %}  maxlength="256"/>
            <span class="help-block">A regular expression that specifies which branches to exclude from the analysis.
              For example, <code>/release-</code> excludes all release branches for project's using that pattern.</span>
          </div>
          <div class="form-group">
            <label>
              <input type="checkbox" name="limit_branch_prediciton_commits" value="limit_branch_prediciton_commits" {% if item.limit_branch_prediciton_commits %} checked="" {% endif %}
                     {% if not item.calculate-branch-statistics %} disabled="" {% endif %} />
              Limit branch risk prediction.
            </label>
            <span class="help-block">Limit the depth of risk predictions on long lived branches to speed up the analysis time.</span>
          </div>
          <div class="form-group">
            <label>Max Commits to Analyse on Branch</label>
            <input class="form-control" type="number" name="max_branch_risk_history_depth" value="{{item.max_branch_risk_history_depth}}" required min="1" 
                   {% if not item.limit_branch_prediciton_commits %} disabled="" {% endif %} />
            <span class="help-block">Skip risk predictions on branches with more commits than the given limit.</span>
          </div>
        </div>

        <div class="tab" data-tab-id="delta-analysis">
          {% include "cacsremoteservice/views/projects/configuration/delta-analysis.html" %}
        </div>

        <div class="tab" data-tab-id="delivery-performance">
          {% include "cacsremoteservice/views/projects/configuration/delivery-performance.html" %}
        </div>
        
      </div>

      <div id='save-config-button'>
        <button class="default-button" type="submit">
          <i class="save-progress-indicator fa fa-check"></i>
          <span data-automation-id="update-project-configuration"
                class="text">Update</span>
        </button>
      </div>
    </div>
</form>
</div>
      
{% include "cacsremoteservice/views/partials/default-footer.html" %}
      
</div>
{% endblock %}