Issue Track/Bug Reporting

Hi,

We are usuing GreenHopper within our team for tracking feature development. As we are starting to make releases we are obviously starting to get bugs back and we are trying to decide exactly how to organise this.

Ideally our customers would report issues via Jira in some way, but we have a lot of users, and I don't want to add them to the development group as that would make GreenHopper difficult to handle.

What I feel I want to be able to do is allow a user to create a ticket that has no influence on current work, in other words unscheduled and unassigned only. This could be triaged and assigned to a person and sprint and then the reporter could comment on it, having to finally sign off. However if the reporter had to sign off on something in, say, Sprint1 and couldn't be relied on to do this in that given timesclae how would I handle 'releasing' Sprint1?

Bit rambling, but I'm just after some advice.

Chris.

Hi Chris,

Please send me your email, I will have Nick Muldoon, PM of GreenHopper, to answer you directly on how we manage this in GreenHopper. I have to admit that what we do seems to work pretty smoothly. The dev do not get distracted by the clients issues and we have a pretty good answer/fix rate.

My email is jchuet [at] atlassian [dot] com

Cheers,
JC