Comments, tickets and restrictions

How pages and tickets refer to each other, comments on pages and passages, who may see or change a page, and a space's settings.

Pages are read and discussed by a team, and some must be kept from part of it. This page covers how pages and tickets link to each other, comments, restrictions and the settings of a space. Writing and organising pages is on Knowledge base.

Pages and tickets

The knowledge base and the tickets know about each other:

• A ticket lists, under Pages, every page that mentions its key and every page linked to it, as far as you may read them. Link a page there links one of the project's pages by hand; it then lists the ticket too, and the link is written to the ticket's history. Remove takes a hand-made link away again.
• In a ticket's description or a comment, [[KEY/Page title]] (or [[KEY/Page title|other words]]) becomes a link to the page, showing its title, for anyone who may read it; for anyone else it stays the text you wrote, so a page's title never reaches somebody it is hidden from. A page's address pasted on its own shows as the page's title too.
• Write it up, on a resolved ticket, starts a page in the project's space with the ticket's summary as its title and a line naming the ticket, so the page and the ticket are linked as soon as it is saved.
• A project's page shows its most recently edited pages, and Knowledge beside its settings opens its space.

Comments

Comments sit under the page. Reply answers one in its thread, and your own comments can be edited and deleted (those who manage the space can change anyone's).

An inline comment is about a passage of the page. Select the words in the page (a few characters at least, in one paragraph or across several) and choose Comment, which appears at the end of your selection: the passage is filled in beside the page, and you write your comment under it. The comment remembers which of the passage's appearances you selected, so the same words earlier in the page are left alone. (You can also type the passage by hand, and trim the passage before posting.) The comment is listed beside the page with the passage quoted, and the passage is marked in the page; click the mark to find the comment, or the quote to find the passage. Resolve folds it away under Resolved, and Reopen brings it back. When the page changes and the passage is no longer in it, the comment is not lost: it is listed under No longer on the text, with its passage struck through, and no longer marked in the page.

Restrictions

Those who manage a space can narrow who sees or changes a page with Restrictions on the page:

• View restrictions name the people and groups who may read the page. They apply to every page below it too, and a page below cannot open itself to more people than the page above allows. The first view restriction you put on a page names you too, so you never hide a page from yourself.
• Edit restrictions name who may change the page; everyone else who can read the space still reads it. They apply to that page alone.

A page you may not read does not appear anywhere: not in the tree, lists, backlinks or search, and its address says there is no such page. Installation administrators are not bound by restrictions; anyone else, a space's managers included, is.

Space settings

Settings, for those who manage the space, changes its name, description and home page, and whether customers of the helpdesk may read the pages marked Published (help articles). An installation administrator can also let public request forms suggest a space's published pages to people with no account. For a workspace space it also sets who reads it and holds its grants: read, write or manage, for every member, a group, the holders of a role or one person. Grants brought from Confluence that Alba has no equivalent for are listed as kept and not applied.