[Summary view] [Print] [Text view]

   1  @title Diffusion User Guide: Autoclose
   2  @group userguide
   3  
   4  Explains when Diffusion will close tasks and revisions upon discovery of related
   5  commits.
   6  
   7  Overview
   8  ========
   9  
  10  Diffusion can close tasks and revisions when related commits appear in a
  11  repository. For example, if you make a commit with `Fixes T123` in the commit
  12  message, Diffusion will close the task `T123`.
  13  
  14  This document explains how autoclose works, how to configure it, and how to
  15  troubleshoot it.
  16  
  17  Troubleshooting Autoclose
  18  =========================
  19  
  20  You can check if a branch is currently configured to autoclose on the main
  21  repository view, or in the branches list view. Hover over the {icon check} or
  22  {icon times} icon and you should see one of these messages:
  23  
  24    - {icon check} **Autoclose Enabled** Autoclose is active for this branch.
  25    - {icon times} **Repository Importing** This repository is still importing.
  26      Autoclose does not activate until a repository finishes importing for the
  27      first time. This prevents situations where you import a repository and
  28      accidentally close hundreds of related objects during import. Autoclose
  29      will activate for new commits after the initial import completes.
  30    - {icon times} **Repository Autoclose Disabled** Autoclose is disabled for
  31      this entire repository. You can enable it in **Edit Repository**.
  32    - {icon times} **Branch Untracked** This branch is not tracked. Because it
  33      is not tracked, commits on it won't be seen and won't be discovered.
  34    - {icon times} **Branch Autoclose Disabled** Autoclose is not enabled for
  35      this branch. You can adjust which branches autoclose in **Edit Repository**.
  36      This option is only available in Git.
  37  
  38  If a branch is in good shape, you can check a specific commit by viewing it
  39  in the web UI and clicking **Edit Commit**. There should be an **Autoclose?**
  40  field visible in the form, with possible values listed below.
  41  
  42  Note that this field records the state of the world at the time the commit was
  43  processed, and does not necessarily reflect the current state of the world.
  44  For example, if a commit did not trigger autoclose because it was processed
  45  during initial import, the field will still show **No, Repository Importing**
  46  even after import completes. This means that the commit did not trigger
  47  autoclose because the repository was importing at the time it was processed,
  48  not necessarily that the repository is still importing.
  49  
  50    - **Yes** At the time the commit was imported, autoclose triggered and
  51      Phabricator attempted to close related objects.
  52    - **No, Repository Importing** At the time the commit was processed, the
  53      repository was still importing. Autoclose does not activate until a
  54      repository fully imports for the first time.
  55    - **No, Autoclose Disabled** At the time the commit was processed, the
  56      repository had autoclose disabled.
  57    - **No, Not On Autoclose Branch** At the time the commit was processed,
  58      no containing branch was configured to autoclose.
  59    - //Field Not Present// This commit was processed before we implemented
  60      this diagnostic feature, and no information is available.