Confluence 4.3 のサポートは終了しています。
ドキュメントの最新バージョンを確認してください。
Labels are key words or tags that you can add to pages, blog posts, attachments and spaces. You can define your own labels and use them to categorise, identify or bookmark content.
Labelling a page or blog post
Any user with permission to edit a page can add a label to a page.
ページやブログ投稿にラベルを追加するには:
- Go to the page. If the page already has labels, these will be listed at the bottom of the page, below the page content.
- Click the edit icon beside the list of labels, or press L on your keyboard.
- Type in a new label. Existing labels are suggested as you type.
- [追加] をクリックします。
Screenshot 1: Labels as they are displayed on a page
Screenshot 2: Adding a label to a page or blog post
Labelling an attachment
Any user who has permission to view or edit the page that contains the attachment can add a label to the attachment.
To add a label to an attachment:
- Go to the page that contains the attachment. Choose Tools > Attachments.
- Alternatively, go to the attachments view of the space:
Go to a page in the space and choose Browse > Attachments.
- You will see a list of attachments, with columns for attachment name and other details. If the attachment already has labels, these will be listed in the Labels column.
- Click the edit icon beside the list of labels.
- Type in a new label. Existing labels are suggested as you type.
- [追加] をクリックします。
You can also add labels in a list of attachments displayed by the Attachments macro, by clicking the edit icon beside each label as described above.
Screenshot 2: Adding a label to an attachment
注意
Note: Personal labels are deprecated: Earlier versions of Confluence recognised a special type of label called a 'personal' label. A personal label starts with 'my:' and is only visible to the user who created it. We are removing personal labels from Confluence, as announced in the Confluence 4.1 Upgrade Notes. The functionality for personal labels is still in Confluence, but we recommend that you stop using them. In a future release, we plan to remove the functionality altogether.