Dependency is empty on the other card | Voters

Dependency is empty on the other card

under review

Elli Hytti

In the card on the development board, we can see the dependency, but on the other card on a different board, the dependency is empty. We have seen this happen three times on different cards

June 18, 2024

Dovidas Baranauskas

Elli Hytti is there a reason why you are copying the card and not just adding it to other locations? Also if you are copying the card it will loose the dependency because it is a copy and not the same card.

Elli Hytti

Dovidas Baranauskas We create a Copy because we need to save the information in two different Collections for archiving purpose. The two different Collections use the same information differently and cannot use the same ticket. 
The dependency is created in the Collection where the copy is made, not before copying a ticket. 
We use Copy purely as a timesaver so we do not need to write same details twice.
Additionally, the reported issue appears sometimes also in tickets that are not copied from another Collection.

Dovidas Baranauskas

marked this post as

under review

Dovidas Baranauskas

marked this post as

open

Dovidas Baranauskas

marked this post as

closed

Dovidas Baranauskas

Elli Hytti, The two cards you are showing are different or a copy of one another. Thus, they are different and not the same. You can see the Card ID on the top left corner is different and also in the On boards menu you do not see that the card is in two different boards.

Elli Hytti

Dovidas Baranauskas Sorry that my report was unclear. I hope that I can clarify this and hopefully get this report opened again:

Yes, these are two different cards: with a same name.
The one on the "PS Bugs & Issues" collection (SMA-122261) is a copy of the one on the Development collection (SMA-122260) created for the other collection for progress and archiving purposes.

Elli Hytti

Dovidas Baranauskas We create a dependency between these cards to keep tabs on the progress and updates on the development ticket. This has been our procedure and method for several years. 
However, recently we noticed that on a few copied tickets, the dependency suddenly does not show/has disappeared while the dependency is still showing on the development card (as seen in my example screenshots). The dependency/link is still active on the development ticket. Usually, if the dependency is removed, it will get removed from both cards.
I hope this has helped to clarify the issue. I'm happy to provide more details as needed.