Disable new posts?

Damien Elmes's Avatar

Damien Elmes

01 Apr, 2013 11:17 PM

Hi guys,

Due to the number of invalid & duplicate reports I get on my issue tracker, I'd like to handle future bug reports via Tender instead. The problem is that I have a number of existing Lighthouse tickets where I may need to follow up with the user before the problems can be resolved. Is there any way to disable the creation of new tickets by non-admin users, while allowing users to continue posting on existing tickets? Or if that's not possible, is there a way to keep the issue tracker publicly readable but disable the ability of non-admins to create & post on tickets?

Cheers,
Damien

  1. 1 Posted by Julien on 02 Apr, 2013 12:50 AM

    Julien's Avatar

    Hi Damien,

    Lighthouse doesn't offer this level of granularity for permissions. You would have to remove users to prevent them from posting to your project. I'll try to think of a better way tonight, or some sort of work-around.

  2. 2 Posted by Julien on 02 Apr, 2013 04:48 PM

    Julien's Avatar

    Hi Damien,

    I'm afraid you will have to move those projects to private, and maybe keep some users as members, or communicate with them outside of Lighthouse if you don't want to keep them as members. I couldn't think of a better way.

  3. 3 Posted by Damien Elmes on 03 Apr, 2013 12:15 AM

    Damien Elmes's Avatar

    Ok, thanks for looking into it anyway. I guess I'll need to use the API to
    post a message on all the open tickets. It would be nice if we could do
    this via a bulk edit in the future - it's something that could be done on
    Google Code, and was useful in times like these.

  4. 4 Posted by Julien on 03 Apr, 2013 05:42 PM

    Julien's Avatar

    Hi Damien,

    If you give me the message and the tickets you want it on (like all open tickets on projects X, Y and Z), I can do it for you.

  5. 5 Posted by Damien Elmes on 04 Apr, 2013 02:35 AM

    Damien Elmes's Avatar

    Hi Julien,

    Thanks, I might take you up on that. Before I move forward, my primary
    concern is being able to reach some users when I have a chance to return to
    specific bug reports. If I recall correctly, Lighthouse (unlike Tender)
    does not make the poster's email address visible to me. This prompts some
    questions:

    - when the project is set to private, I presume all the non-admin posters
    will be removed from the project. Will their comments remain, along with
    their name?
    - I presume their email subscriptions will also be removed, so I can't just
    reply to the ticket and have them see it?
    - If so, would it be possible to get a CSV mapping of username->email in my
    projects, so if I need to contact someone and have their name, I can look
    up their email address?

    Cheers,
    Damien

  6. 6 Posted by Julien on 04 Apr, 2013 05:41 PM

    Julien's Avatar

    Thanks, I might take you up on that. Before I move forward, my primary concern is being able to reach some users when I have a chance to return to specific bug reports. If I recall correctly, Lighthouse (unlike Tender) does not make the poster's email address visible to me.

    True. You can have the users ID, but not their email.

    when the project is set to private, I presume all the non-admin posters will be removed from the project. Will their comments remain, along with their name?

    Their comments and name will stay.

    I presume their email subscriptions will also be removed, so I can't just reply to the ticket and have them see it?

    Indeed. They won't receive any notification.

    If so, would it be possible to get a CSV mapping of username-email in my projects, so if I need to contact someone and have their name, I can look up their email address?

    I think we can work something out, but I need to check with the rest of the team, as this is not something Lighthouse makes normally available. I'll give you an answer later today.

  7. 7 Posted by Julien on 04 Apr, 2013 07:18 PM

    Julien's Avatar

    So, the answer is a no on the CSV front. It's against our TOS and the consensus was a no.

    Your best solution at this point would be to use Tender API and Lighthouse API to:

    • Create a discussion for each ticket
    • Give the discussion URL in the notice message and tell people to go and subscribe there.

    Tender's API doesn't allow you to do ticket assignment, but you could post an internal message with the ticket URL, and would have references back and forth.

    It somewhat not as easy as it could/should be, but it's a working solution.

    Let me know what you think.

  8. 8 Posted by Damien Elmes on 05 Apr, 2013 12:59 AM

    Damien Elmes's Avatar

    Hi Julien,

    Ok, it sounds like my best bet is to hold off on closing the old issue
    tracker for now, until I have a chance to sort through the outstanding
    issues and create threads about them on Tender.

    Cheers,
    Damien

  9. 9 Posted by Julien on 05 Apr, 2013 05:06 PM

    Julien's Avatar

    Hi Damien,

    Sorry we couldn't offer you a better way at the moment. I will close this discussion, but feel free to re-open it again as needed.

    Thanks.

  10. Julien closed this discussion on 05 Apr, 2013 05:06 PM.

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