Creating a generic issue Tracker macro is probably a challenge. For each tracker, you need to provide:
* An URL pattern
* A default Text pattern
The macro should be able to handle multiple trackers at the same time.
Examples:
== Bugzilla installed at the Eclipse foundation:
Issue Id is a number.
* Text: "Bug {id}"
* URL:
https://bugs.eclipse.org/bugs/show_bug.cgi?id={id}
== GitHub
I think we would create one tracker for each project. Issue Id is a number.
For Asciidoctorj
* Text: "#{id}" or "asciidoctor/asciidoctorj#{id}"
* URL:
https://github.com/asciidoctor/asciidoctorj/issues/{id}
And Asciidoctor.org:
* Text: "#{id}" or "asciidoctor/asciidoctor.org#{id}"
* URL:
https://github.com/asciidoctor/asciidoctor.org/issues/{id}
== JIRAs
(See the JBoss Tools macro). Another example with the public Jenkins JIRA instance:
Issue Id is a String "JENKINS-35666"
* Text: "{id}"
*
https://issues.jenkins-ci.org/browse/{id}
The way I see it for the moment, it would be nice to define a second parameter host or server.
issue:<id>[host, optional text]
At document level as many variables are defined as necessary (see the values above)
issue-url-eclipse
issue-text-eclipse
issue-url-jenkins
issue-text-jenkins
If no host is defined in the macro, the default variables "issue-url" or "issue-text" are used.
In the text you can write something like:
Check the related issues to this problem issue:0234[eclipse] or issue:JENKINS-35666[jenkins].
Please note that issue:ROASTER-105[jboss] is also relevant.
Locked
