I suggest you ...

Let two cards have the same external ID

The ability to add an external ID is cool, but a limitation is that
two cards cannot have the same external ID. The board prevents saving
when that is attempted:

Error

An error occurred while updating the Card. Error: Card you are
trying to save contains External Card ID that already present on
this board. You must provide unique External Card ID for this Board
in order to be able to save this card.

Please can you make it possible to associate more than one card with
the same external ID? Perhaps as a configuration option.

Thanks, Gavin.

25 votes
Vote 0 votes Vote Vote
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service

    You'll receive a confirmation email with a link to create a password (optional).

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Gavin PanellaGavin Panella shared this idea  ·   ·  Admin →

    3 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service

      You'll receive a confirmation email with a link to create a password (optional).

      Signed in as (Sign out)
      Submitting...
      • Vic ThomasVic Thomas commented  · 

        Having unique external IDs is important to us, as we synchronize via the API with our ticketing system in a one-to-one relationship between tickets and LeanKit cards. The uniqueness constraint makes the integration simpler. So, I like the configuration option mentioned earlier so that this important piece of functionality does not change unexpectedly.

      • JekJek commented  · 

        We have this same issue. There is no reason that an externally referenced resource be limited to one card. If a user/application wants them to be unique, then it could enforce uniqueness (by looking it up first). StewS's workaround doesn't support the auto-link generated or simultaneous sessions (all trying guess what the next letter would be).

        To support this, the API would return all the cards with the external ID requested.

        If guaranteed uniqueness is felt required by the LeanKit team, then at least give us a checkbox to enable/disable this behavior.

        One other option: You could give us a way to write the header and link via the API, without it being the external ID. However, we'd have to be able to query that as well.

      • StewSStewS commented  · 

        Rats, I didn't notice it worked this way! (I'm still using the Free account, which doesn't allow external IDs).
        I guess I'll have to put an "a", "b", etc at the end to make them unique?

      Knowledge Base and Helpdesk