The way the greenhopper application appears to function is that for every project there is a dedicate development team allowing for easy planning and working at individual project levels. We only have a small development team and many of those developers are involved in different projects which greenhopper does not appear to cater for. Assuming you have other customers or perhaps first hand experience of the issues faced in this situation you could offer some advice? For instance how can we do effective planning of resource for one project when some of the developers are involved in other projects and therefore can not provide their full dedication to one project? From our perspective we need a governing project/view that we can use to plan work for all projects based on available resources spread across these projects. Any help/advice you can offer would be appreciated. Kind Regards.
This is not uncommon, crops up fairly regularly with consulting companies.
What you may like to do is have a Scrum board that includes a number of JIRA Projects, one for each customer perhaps. You can then create a sprint for the whole team that includes the work of various clients, allowing you to build a single sprint backlog for all work.
You can add multiple projects to a single Scrum board via Tools -> Configuration -> Filter -> Manage Filter -> Edit, and from there add more projects as needed.
Take a look and let me know if that works for your environment.