Plugin to Link to Another Redmine Instance?
Added by David Stahl about 15 years ago
We have two Redmine instances.
The Company Redmine is used to track low-level development issues for a long-term software project.
The Client Redmine is used more for program management, but some issues may be in both the Company and the Client Redmines (let's say there's an issue for a big new feature that appears on both schedules).
What we have done is to create a custom field in each Redmine called "Vendor Issue Number:" and we populate that so that we can follow them back & forth.
What I wanted to do was have a way to tell Redmine that that custom field is an issue number in a foreign Redmine and let it automatically set up a link to it for me.
Is there a plugin already to do this? If not, I was going to write one. Any interest?
Replies (2)
RE: Plugin to Link to Another Redmine Instance? - Added by Mischa The Evil about 15 years ago
David Stahl wrote:
[...]
What I wanted to do was have a way to tell Redmine that that custom field is an issue number in a foreign Redmine and let it automatically set up a link to it for me.Is there a plugin already to do this?
[...]
No, not that I know of.
RE: Plugin to Link to Another Redmine Instance? - Added by David Stahl about 15 years ago
I've got a usable plugin, but I've got one issue that would make it much nicer: How can I add a customer rendering for a custom field?
What I wanted to do was add a hook or something so that when a custom field with the name "Client Issue ID:" was being rendered, my plugin could render it as a hyperlink instead of just the value.
So far I haven't seen a mechanism built in to RM for it, but is there a way to do it without hacking up the Core?
I've read in other places that it's possible to overwrite a view (http://www.redmine.org/wiki/redmine/Plugin_Internals), but I'd like to not have to create a new view for the issue display page just to make that field a hyperlink.
Any thoughts or suggestions for the proper way to do this? I think what I'm looking for is a way to filter certain things before they're rendered. Specifically, a custom field on an issue.