Tickets should have names consisting of project name + numbers for better identification and sharing possibilities. One example would be to refer to several tickets from several projects in any kind of message.
Tickets can actually be referred to across projects as [kajiki:tickets:#15] already
status: open --> invalid
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2011-05-16
Originally by: warjan
That's nice. Is it automatic? I mean: If I'd like to commit a change fixing bug #100, should I write just fixing #100 or [tonic-chess:tickets:#100]? Where can I find some help for tickets and tracker-scm integration?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Tickets can actually be referred to across projects as [kajiki:tickets:#15] already
Originally by: warjan
That's nice. Is it automatic? I mean: If I'd like to commit a change fixing bug #100, should I write just fixing #100 or [tonic-chess:tickets:#100]? Where can I find some help for tickets and tracker-scm integration?
Yes, it's all automatic. Unfortunately we don't have great documentation on all the cross-linking yet. All shortlinks are of one of three forms:
So if you're committing to a repo in the same project as your tracker, your message should be
This also works with wiki pages, etc (wiki page links are of the form [Allura Wiki] )
Related
Tickets:
#100Wiki: Allura Wiki