| Name | TagLinks |
|---|---|
| Vendor | Comala Technology Solutions, Inc. (Website) |
| Authors | |
| Homepage | http://confluence.atlassian.com/display/CONFEXT/TagLinks |
| Issue Management | http://developer.atlassian.com/jira/browse/TGLNK |
| Continuous Integration | n/a |
| Categories | Content Macros |
| Most Recent Version | 1.0.2 |
| Availability | Confluence v2.3.3 to v2.10 |
| State | Stable |
| Support |
|
| License | Freeware / Open Source (BSD) |
| Price | Free |
| Release Docs | n/a |
| Java API Docs | n/a |
| Download Source | http://www.comalatech.com/confluence/plugins/src/taglinks-1.0.2-src.jar |
| Download JAR | taglinks-1.0.2.jar |
| This plugin now accessible through the Confluence Repository Client. |
Description/Features
Allows pages whose titles match a pattern (<id>.<id>.<id>...) to be handled hierarchically, by automatically storing them as children of higher-level pages and rendering any reference to them as links, without having to explicitly declare them as such using '[' and ']'.
Usage
After installing this plugin:
- Whenever you create or modify pages with a title following the naming convention, they will be stored hierarchically, regardless of where they are created
- Anytime there is a reference to any of the tags in Confuence's content, they will be rendered as links. References to the tags will be rendered as links including references to the parent-pages in the hierarchy
Examples
Lets say a collection of use cases and each title follow the form uc.<id>.<id>...:
- uc.purchase
- uc.purchase.digital-content
- uc.purchase.digital-content.single-product
- uc.purchase.digital-content.shopping-cart
- uc.purchase.hard-goods
- uc.purchase.hard-goods.shopping-cart
- ...
And lets say you create a table:
|| Use case || Iteration || Comment ||
| uc.purchase.digital-content.single-product | 1 | working on it... |
| uc.purchase.hard-goods.shopping-cart | 3 | |
| uc.purchase.digital-content.shopping-cart | TBA | Not defined yet |
It will render as follow:

The links created include links to parent tags. For instance uc.purchase.digital-content.single-product is made of links to uc.purchase, uc.purchase.digital-content and the actual link to uc.purchase.digital-content.single-product, depending on where you put the cursor:



Installation
Configuration
You can configure how the tags are to be treated, or even define the pattern (regular expression). All configuration is done through the configure plugin link in the Plugin Manager.
| Setting | Description | Default |
|---|---|---|
| Separator | what separator to use to delimit the hierarchies in the tag | . (period) |
| Links | Links generated could include parent-page or just the given page | Generate links including parent-pages in the hierarchy |
| Prefixes | You can define a comma-separated list of prefixes (i.e. uc, reqs) the tags must have to be treated as links | Empty |
| Regular Expression | You can actually change the Regular expression used to identify the Tag pattern. The regular expression should refer to the SEPARATOR and handle the groups the same way is in the default. | long and complicated |
Version History
| Version | Description |
|---|---|
| 1.0.2 | Fixed TGLNK-2 and TGLNK-3. TGLNK-4 is still outstanding, but you can work around it by using Prefixes, as defined above |
| 1.0.1 | http://developer.atlassian.com/jira/browse/TGLNK-1 |
| 1.0 | First public release |
Screenshots
About tagging
From Principles of Software Engineering Management by Tom Gilb, 1988:
- Mnemonic tags don't get obsolete (as numbers do) by additions or removals
- They convey more meaning when cross referencing from other documents
- They are useful to summarize the gist of an idea and headline it

