We are purchasing a 25 user license for JIRA and GreenHopper and are beginning to plan our migration from JIRA 3.x. We heavily customized our current version of JIRA and don't wish to do that again.
We have a single team that develops 5 different web applications. What is the best way to configure JIRA and GreenHopper for a scenario like this?
1) Should we create a single JIRA project with 5 JIRA Components? How would we keep track of features in this case?
2) Should we create 5 different JIRA projects (one per web application) and use JIRA Components for the features of each application? As Project Manager, would I be able to get work or issue reports across all projects?
I'm just looking for best practtices from the community. We heavily customized our current version of JIRA and are not looking to do this again.
We have a similiar setup, where we have a small development team but many web applications that we develop for. We've decided to setup each web application as it's own JIRA project. We also setup a seperate JIRA project for other types of issues: we have an ADMIN project that our office assistant uses for business admin type tasks, and an OPERATIONS project that houses non-project specific server and infrastructure related tasks.
This seems to work well for us, and now with the new GreenHopper we exclusively use the Rapdid Board to manage it all. In the Rapid Board, you can combine projects into one agile "white board". Also, for more traditional issue queries, it is easy to combine results cross project.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG