ticket/133742 will become project/babar/ticket/133742. | |
| priority | normal |
|---|---|
| type | enhancement |
| appeared in | <not specified> |
| done in | <not specified> |
| load | 0.000 |
| load left | 0.000 |
| closed by | <not specified> |
| CubicWeb's Forge | anonymous [register] [login]
|
cubicweb-tracker #1352144 prefix ticket absolute url with the project name [rejected]
|
|||||||||||||||||||
Comments
-1
I don't want ticket's url to change when reaffected to another project.
This case have of course to be handled. But having the project name in the url would me much more informative url.
couldn't we handle:
so as to satisfy both needs ? (here /totor/0.2.0 would be a purely informative piece without impact on ticket lookup)
project/babar/ticket/133742 contains the ticket eid so their is no issue for ticket lookup. if ticket 133742 move from babar to tortue we can either:
how would you handle it? And 'informative' url are useful when that
makes it easy to remember them. It's not the case here, you still have
to remember ticket's number.
I would handle it with a cute urlrewrite (or its brother) hack.
If the project/version changed, I'd tell the user, as a bonus.
The biggest obstacle is tolerance to obsolete information, from users.
An informative url is also usefull/important to recognise an url. With the project name the ticket url is less anonymous and help people to know what the url is about before opening it.
apycot test execution url contains environment and test config name and the execution eid. This help people to know if they might be concerned by a pasted url.
the ticket part of the absolute url for example doesn't help to remember of lookup a ticket. It only help to recognise that this entity is a Ticket
cool uris don't change. /ticket/12345 is the way to go. please reject this.
should this ticket be marked as "rejected ?