Do you have any guidance on how to use various link types while linking stories

[jinu john]

I have story A which is waiting for completion of Story B. I was planning to link them.

Do you formal definition of guidance on when to use which link type?

Link issues | Jira Cloud | Atlassian Support

[Dick]

Hi @jinu john Welcome to the Atlassian Community. 

Some practicalities when using linked stories:

Blocks  -   Use this if you're having stories that are truly sequential and the subsequent story can only be carried out when blocking story is done. Think in terms of a recipe of baking cookies. 

Is blocked by  -  Similar as with Blocks, but looking from the subsequent story "ratting out" the story that prevents completion

Clones - You can clone a ticket from one project into another. Like from project/team focused on production to a project/team focused on quality control.

Is cloned by - similar as Clones, but looking from the cloned issue

Duplicates  -  When a user finds that a ticket is more or less the same as another ticket. It can signal 

Is duplicated by - similar to Duplicates, but looking from the oldest issue.

split to  -  When an issue is sliced into smaller bits

Is split from  -  similar to Split to, but looking from the newer issue containing part of the work.

Relates to  -  Can be used for indicating a cause-effect relation between tickets (think configuration change ticket and related bug that reared its head as a result of the change.

The above is not intended to cover all possible kinds of relations between tickets. It merely serves as an indication on how you could use issue linking yourself. 

Kind regards,

Dick

[jinu john]

Thanks a lot Dick for quick response ! Could you also explain all other field ( particularly depends on and depended by)

[Dick]

Hi @jinu john, those are not present in the version of Jira I'm using, but it can only be that these are used to formulate prerequisite conditions. 

This is in contrast to blocking issues that by not being finished cannot pass vital information to the subsequent issue.

Bear in mind that I'm a non-native speaker trying to read the minds of the developers here. 

You can find more interpretations of this in this link

Kind regards,

Dick