Account wide IDs

Ask Bjørn Hansen's Avatar

Ask Bjørn Hansen

04 Jun, 2009 06:34 PM

For permission and administrative reasons we have several "projects" in LH. They have some overlap in the code bases though, so now we have to prefix all our references to tickets etc with "someproject#123" rather than being able to just talk about ticket #123.

We'd like an option to have the bug ids increment globally (by account) rather than individually by project.

  1. 1 Posted by Ask Bjørn Hanse... on 11 Jul, 2009 12:37 AM

    Ask Bjørn Hansen's Avatar

    Any chance of this happening? If not then using LH won't scale for us for future projects (we need some access control / separation of tickets, and the only way to do it is with projects).

  2. 2 Posted by Rick on 11 Jul, 2009 03:16 AM

    Rick's Avatar

    Very little chance, sorry. I could implement project-wide ticket IDs though, like #PROJECT-TICKET (#123-123 or maybe even #project-a-123) if that would work.

  3. 3 Posted by Ask Bjørn Hanse... on 13 Jul, 2009 05:05 AM

    Ask Bjørn Hansen's Avatar

    Darn - that's too bad. I was hoping since you (somehow) generate the IDs already, it'd be possible to have a "generate by account" instead of "by project" toggle. #project-a-123 is what we do internally; but it's not really practical.

    We use the IDs both in conversation (verbally, irc, email, ...) and in branch names in git, so always remembering to use the prefix is a pain.

  4. 4 Posted by Rick on 13 Jul, 2009 07:10 AM

    Rick's Avatar

    We do generate them, but there's a project-wide unique index for them. I wish I could toggle that, but it's not so simple.

  5. 5 Posted by Ask Bjørn Hanse... on 15 Jul, 2009 06:07 PM

    Ask Bjørn Hansen's Avatar

    This still makes no sense to me; it seems like you could add an account-wide index for accounts that have the feature enabled and use that for the IDs -- but obviously you know how your system is built and I don't. At least you have APIs for if/when we need to migrate the data! :-)

  6. 6 Posted by Rick on 15 Jul, 2009 06:32 PM

    Rick's Avatar

    There's a unique index on project_id and number, I can't really add an
    optional number index. There are other more complex things I can do,
    but I can't justify it for a single account. It adds more complexity
    in the application all over the place. Sorry it doesn't fit your
    specific business case. Yes, we have an API and you can request a
    JSON dump too.

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