Since GreenHopper boards are based on JIRA filters, you can have as many boards you wish, with any JIRA issues you need your team to work on. There are loads of distinct ways to work with the boards, and each team must find its own way, but a very popular flow is to create a board for each JIRA project (as mentioned by Tanner). With that you can have different teams working on individual projects/boards at the same time.
Hope it helps,
Old topic, but still relevant. It seems to me that any useful metrics would be blown up if you've got a single guy working on many projects while using different boards for each. Say Project A and B have different statuses and are accessed by two different boards. Wouldn't hopping back and forth with breaks in activity in each task board would make it impossible to judge workload? Additionally, if Project A doesn't have an In Progress status, then what happens when reporting from Board B - ignored status?
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
...PermissionsStartOnly=true User=www-data Group=www-data ExecStart=/opt/jira/bin/startup.sh ExecStop=/opt/jira/bin/shutdown.sh TimeoutStartSec=120 TimeoutStopSec=600 PrivateTmp=true [Install] WantedBy...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs