I was testing out linking cards and came across a scenario that results in unexpected & impolite behavior.
Clicking on a dead card link, when card was on a different board and that board has since been deleted, but the linked card wasn't explicitly deleted
Given I have two boards: "Strategery" and "App27"
and I have a card on board "Strategery", and the card is titled "Plan"
and I have a card on board "App27", and the card is titled "Minor Feature"
and I placed a link to board "App27" > card "Minor Feature" in the description of board "Strategery" > card "Plan"
When I delete board "App27"
And open board "Strategery" > card "Plan"
And click on the link to board "App27" > card "Minor Feature"
Then I should see an error message letting me know that card no longer exists
And I should still be on board "Strategery"
And the details of card "Plan" should still be visible // (so I might delete or replace the broken link)
And I should most certainly still be logged into Glo/GitKraken
But what actually happens is that the session gets terminated and I get shown the login screen. I imagine this is a low priority issue - since everybody using this will be developers on small teams, they'll have a good idea of what caused the error, and their reaction will just be "understandable, have a nice day". But the solution to this problem will be useful for future features, I'm sure. (Hovering card links to get a preview of the card, transferring cards between boards, establishing card relationships and displaying status of the related card, etc.)
Decided to test a few other scenarios. Here's my notes:
Link to a card that exists on a different board. Delete the board. Click link. (session killed, sent to login)
Link to a card that exists on a different board. Delete the card only. Click link. (sent to other board, which is nice, but no error about the card not existing. If there was lots of content and I was a product manager that only checks in every 2 weeks, I'd be very confused.)
Link to a card that exists on same board. Delete card, click link. (card description closes, no error message. same behavior as above basically)
Link to a card that never existed on same board. Click link.(card description closes, no error. Same as 3)
Link to a card that never existed on a different board that currently exists. Click link. (other board loads, same as 2)
Link to a card that never existed on a board that never existed. Click link. (description closes, board closes, but then the board loads up again.
Hmm: Link to a card that exists on a different board. Delete the linked card first. Then delete the list the card was on. Then delete the board. Click link. (This actually doesn't sign the user out. This just closes the description and reloads the current board, like 6. So I'm thinking the bad behavior in scenario 1 stems from the fact that the card still exists in the database, and probably has null values for permissions or board or list or something.)
Link to a card that exists on a different board. Delete the linked card. Don't delete the list. Delete the board. (Board reloads, same as 6. )
All scenarios up there aren't ideal experiences. Just a little error toast is all that's needed I think.
No error messages are being output to developer tools console (not even on the logout event).
Session logout only seems to happen when linking to a card that still exists (i.e. the card itself wasn't explicitly deleted) This makes me twitch a little. Personally, I'd like to know that if a board gets deleted, all the cards get deleted along with it. Unless it's like trello where it's practically impossible to ever delete anything...
I was testing out linking cards and came across a scenario that results in unexpected & impolite behavior.
Clicking on a dead card link, when card was on a different board and that board has since been deleted, but the linked card wasn't explicitly deleted
But what actually happens is that the session gets terminated and I get shown the login screen. I imagine this is a low priority issue - since everybody using this will be developers on small teams, they'll have a good idea of what caused the error, and their reaction will just be "understandable, have a nice day". But the solution to this problem will be useful for future features, I'm sure. (Hovering card links to get a preview of the card, transferring cards between boards, establishing card relationships and displaying status of the related card, etc.)
Decided to test a few other scenarios. Here's my notes:
Hope this helps.