Re: How to make Jira issues appear at URLs like PROJECT.apache.org/issue/NUMBER
Rich Bowen wrote: > I suspect that you could do this with a combination of: > > * mod_rewrite RewriteRule [P] (proxy) rules [...] > * mod_substitute, or mod_proxy_html rules to munge the content [...] I did spend some time playing around with that sort of magic and managed to get some parts of Jira showing up correctly. For a simple app this technique works OK, but I quickly came to the conclusion that for a complex, closed-source app a completely working configuration is unlikely to be feasible (unless it's explicitly supported by Atlassian -- which I haven't checked). > OR > > Work directly with Infra to make something like this happen [...] Sure, I can ask. Thanks for the suggestions. In terms of "community development", I'd love to know if anyone besides myself cares about this or has set up stuff like this for their project, because I feel it's simply the Right Way to do things and yet is commonly neglected. - Julian - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: How to make Jira issues appear at URLs like PROJECT.apache.org/issue/NUMBER
There's two possible approaches that come to mind I suspect that you could do this with a combination of: * mod_rewrite RewriteRule [P] (proxy) rules RewriteRule ^/issue[^A-Za-z0-9]?(\d+)$ https://issues.apache.org/jira/browse/SVN-$1 [P,L] ProxyPassReverse /issue https://issues.apache.org/jira/browse/ (Untested, but looks right) * mod_substitute, or mod_proxy_html rules to munge the content of the actual returned pages (For implementation help, perhaps a longer discussion not on this list would be warranted.) OR Work directly with Infra to make something like this happen with some kind of virtualhost mapping to issues.apache.org, or ... something. On 2/13/19 6:50 AM, Julian Foad wrote: > In Apache Subversion's .htaccess we have this RedirectMatch rule: > > RedirectMatch ^/issue[^A-Za-z0-9]?(\d+)$ > https://issues.apache.org/jira/browse/SVN-$1 > > It redirects a URL like > https://subversion.apache.org/issue/4567 > to > https://issues.apache.org/jira/browse/SVN-4567 > > Why? Human-friendly, technology-neutral, project-owned URLs. Previously we > used a completely different issue tracker (Bugzilla/Issuezilla hosted at a > different site) and a corresponding rewrite rule. The redirect enabled some > of our references to issues to remain stable when we migrated to a different > tracker. That's just one of the reasons for it, perhaps not the most > important one. > > But... a redirect gets us less than half way, because it doesn't map the URLs > displayed in the browser back the other way. In practice, the URLs we write > in email, in code comments, etc. are often copied straight from the browser; > we don't bother to manually translate them back to neutral form. > > So... How can we do this properly? I assume it requires native support from > Jira, which I assume exists because its the sort of thing enterprise > deployments would want. > > More generally, I would like to discuss and learn about anybody's efforts to > achieve anything similar for any of a project's web resources -- wiki pages, > commits, mailing list posts, etc. (What should I call this topic?) > -- Rich Bowen - rbo...@rcbowen.com http://rcbowen.com/ @rbowen - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
How to make Jira issues appear at URLs like PROJECT.apache.org/issue/NUMBER
In Apache Subversion's .htaccess we have this RedirectMatch rule: RedirectMatch ^/issue[^A-Za-z0-9]?(\d+)$ https://issues.apache.org/jira/browse/SVN-$1 It redirects a URL like https://subversion.apache.org/issue/4567 to https://issues.apache.org/jira/browse/SVN-4567 Why? Human-friendly, technology-neutral, project-owned URLs. Previously we used a completely different issue tracker (Bugzilla/Issuezilla hosted at a different site) and a corresponding rewrite rule. The redirect enabled some of our references to issues to remain stable when we migrated to a different tracker. That's just one of the reasons for it, perhaps not the most important one. But... a redirect gets us less than half way, because it doesn't map the URLs displayed in the browser back the other way. In practice, the URLs we write in email, in code comments, etc. are often copied straight from the browser; we don't bother to manually translate them back to neutral form. So... How can we do this properly? I assume it requires native support from Jira, which I assume exists because its the sort of thing enterprise deployments would want. More generally, I would like to discuss and learn about anybody's efforts to achieve anything similar for any of a project's web resources -- wiki pages, commits, mailing list posts, etc. (What should I call this topic?) -- - Julian - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
