Configure defaults for issue fields

Repository administrators can configure the components, milestones, and versions associated with a project's issues. When creating issues, users select these values from their corresponding dropdown lists.  You can specify defaults for each as well. For example, you can configure a General component to use as a default. If a user doesn't choose a component, the system automatically sets the component for the user. This page contains the following topics:

The issue tracker is a light weight feature. If you want a sophisticated issue tracker, you should look into connecting Bitbucket Cloud to Jira Software using the Jira DVCS Connector.  Atlassian has Jira Software subscriptions starting at $10.00 a month.

Deleting existing issue configurations

After you create a component, milestone, or version, users can start using them immediately. Later, you can delete a configuration from the issue tracker. For example, you can create an issue component called Oracle and later remove it. When you remove it, Bitbucket does the following:

  • locates issue's that use it
  • remove the component type
  • leaves the issue's component value empty
  • adds a comment to the issue explaining the change

Bitbucket does the same procedure if you create a milestone or version and later remove them.  

Component configuration

You use components to divide project issues into logical groups. Examples of component names:

  • User Interface
  • Installer
  • 関連ドキュメント
  • プラグイン
  • マクロ

To configure components, do the following:

  1. Go to the repository settings.
  2. Click Issue tracker from the left hand tabs.
  3. Enter the name of the component in the Components section.
  4. Click Add component.

Milestone configuration

A milestone is usually seen as a subset of a version. It is a point that the development team works towards. It corresponds to a short period of time in which the development team implements and delivers a discrete product increment, such as a working milestone release. Examples of milestones:

  • M1
  • M2
  • V1.1.m1
  • V1.1.m2

The system sorts milestones alphabetically.  To add a milestone, do the following:

  1. Go to the repository's  settings.
  2. Click Milestones in the left hand navigation.
  3. Enter a version name.
  4. Press Add.
  5. Optionally, press the default toggle to indicate a version is the default.

Version configuration

Versions are points in a project or product timeline. For example, in a software development project, a version could be a release number. Versions help you schedule and organize your projects and track where an issue had impact. Examples of versions:

  • 1.0
  • 1.1
  • 1.1.1
  • 1.1.2
  • v1.0
  • v1.1

To configure versions, do the following:

  1. Go to the repository's settings.
  2. Click Versions in the left hand navigation.
  3. Enter a version name.
  4. Press Add.
  5. Optionally, press the default toggle to indicate a version is the default.

Set a default Component, Milestone, or Version for all Issues

You can set default issue values for Components, Milestones, and Versions. These default values appear as the initial settings when a user creates an issue. To set default issu e An administrator can set the default component, milestone, or version for new issues.  The process for setting a default is identical

  1. Go to the Components page (or the Milestones or Versions page depending on what you want to set).
  2. Select the default component by clicking the default toggle.
最終更新日 2017 年 9 月 13 日

この翻訳に満足しましたか?

はい
いいえ
この記事についてのフィードバックを送信する

お探しの情報が見つかりませんか?

コミュニティへの質問

Powered by Confluence and Scroll Viewport.