A couple of questions
Hello, I'm investigating migrating away from our current in-house bug tracking tool to a hosted solution. I've created a trial account, tried it a little bit and find myself with a couple of questions:
1) Is there a way to add a release field on incoming issues? The default seems to be more geared toward SAAS-like projects, where fixes go live and affect everyone. We have many releases, and it's important to know where the issue was encountered: A customer using a specific version, or e.g. one of our public betas.
2) Is there a way to have a separate workflow for security issues, so that they aren't public but only visible to the reporter and company staff?
3) Is there another way to make bugs private, in case a customer provides confidential data to ease reproducing it?
4) How can you get a priority field? I read another thread saying it available at settings, but I can't find it there.... maybe it is hiding in plain sight. We have a huge existing set of open and closed issues, and it does need partitioning.
Discussions are closed to public comments.
If you need help with Lighthouse please
start a new discussion.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Will Duncan on 04 Aug, 2010 10:22 PM
Lighthouse isn't really a customer support tool in the wide scope. Yes, you can do public projects, but you have to register to submit and the workflow gets muddy when you let all your clients/customers in.
We built http://tenderapp.com for this purpose, with Lighthouse syncing features so you can have a private and clean development tickets and keep the public side in something more efficient.
You would have to have a separate project for security issues that was private, wouldn't work well to let users in there.
Again, I'd say you should use Tender for these situations. Lighthouse eis a ticket tracker for project development, not a customer support tool.
Lighthouse was not designed to be a priority based workflow. You can sort tickets in order in a milestone, which is more efficient to how the system was designed. With that said, You can enable priorities in your project settings if you are on a Bronze level plan or higher.
2 Posted by teg (at ez) on 05 Aug, 2010 05:00 AM
It is not intended as a support tool (our support team use salesforce for that), but as the software we sell is open source we do have a public bug tracker - operating the same way that Red Hat does with their public bugzilla tracker.
Also, there is no concept of releases of a software to report bugs against?
3 Posted by Will Duncan on 05 Aug, 2010 10:47 PM
I'd suggest using tags or milestones for release versions, but it's not something that's built in, as in there isnt a field in the submissions area for that.
Nicole closed this discussion on 14 Oct, 2010 03:47 AM.