Jira (PUP-1668) Redmine Pages need pointers to JIRA

[Charlie Sharpsteen (JIRA)]

Title: Message Title

Charlie Sharpsteen commented on an issue   Re: Redmine Pages need pointers to JIRA So, there are two viable paths forward here: We can modify the Redmine templates so that a banner is displayed site-wide no matter which page is being looked at. We can edit the home page and project descriptions of public facing projects. Projects that have been migrated to JIRA can get a pointer to their new homes on JIRA. Projects that are defunct can get a EOL notice or get archived/pruned. Option 1 would require a quick "custom patch" to the Redmine code base which may not be desirable. Option 2 would require a bit more work, but would also avoid causing confusion in internal projects that are actually still active — such as the Operations Inventory and Presales Support Queues. Regardless of what we choose to do, we should probably look into pruning dead projects from Redmine. Doing some cleanup will make the archived information easier to maintain going forward. Add Comment   Puppet / PUP-1668 Redmine Pages need pointers to JIRA Given that most people solve problems via Google, and the current first hits for google with the search 'puppet bug report' goto the old Redmine site, it would be very helpful if the redmine site could have a notation somewhere ( header perhaps ) that lets users know the site is depreciated and please go use the new Jira site. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.