Loading...
 

Short and clean URLs for tracker items by default (don't put the title into the URL)

Status
Open
Priority
5 Nice to have
Task
Short and clean URLs for tracker items by default (don't put the title into the URL)
Add a timesheet
Add a timesheet for this task
Description

No bug tracker that I know of (GitHub, GitLab, Bugzilla, Mantis, Trac, RedMine, Phabricator, etc.) dumps the title into the items' URLs. That's just cruft, visual noise that nobody can re-type from memory or when "shouted across the room during a hackfest or by a coworker in the next cubicle", and SEO doesn't matter as much for tracker items (they are not the same intended usecase as wiki pages and such). The current behavior makes for ludicrously long URLs whenever you paste them somewhere, or in the source code of wiki pages, which is annoying.

If you want to render fancy stuff with titles within wiki pages, then expose the title through opengraph metadata and have Tiki look for that metadata when rendering the links on-the-fly in pages.

Tiki already only considers the $tracker_name$item_number part to be the only canonical part, so truncating to only that by default would not break anything anyway. The Discourse forums software exposes titles in URLs (possibly for SEO) but they do have automatic redirects all over the place and the canonical part is still the numbers, not the words, and frankly I don't really see why they bother with that words cruft in the URLs.

Ideally, Tiki's URLs format should be $tracker_name/$item_number (with a clean "/" visual separation) rather than all stuck together with no separator (which looks/feels unpolished), or $grouping_or_project_name/$tracker_name/$item_number (ex: "cypht/issues/435"). This is how I've seen it done nicely elsewhere. I would tend to think it should be simple & clean by default, and if you have an option for the elongated version, then that can be the optional (non-default) behavior, because the only case where I can imagine this being a feature is SEO, and it's a very niche usecase that I'm not even sure is valid except in some corner cases.

Emails
Assigned to
developer
Also visible to
1- Visible to Anonymous (Public content)
Related
Created
Monday 15 of August, 2022 12:08:51 EDT
by Jeff Fortin T.
LastModif
Wednesday 05 of October, 2022 00:58:47 EDT