nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Link ticket "is story of" linktype

Tamas Salamon

I tried this a few times and wondering if there is a bug in jira

So I create a few stories and then create an epic for the stories

I go back to the stories and link them to the epic, using the link and link type "is story of"

I save and it looks right

When I open the epic to verify the link, the linktype shows that it is a bug

Is there some predefined linktype value and it overrides my selected type ?

I know there is an epic link field in a story template but should this not also work ?

Accepted answers

Alex_dddmmh

Hi @Tamas Salamon, and welcome to the community!

The linking between Epics and other standard issues (Stories, Bug, etc.) is established by the Epic Link field on the standard issue. Therefore you might use these two methods to get it working:

1 - Create issues from the Epic

Navigate to your Epic issue and hit Create Issue in Epic

2 - Edit the Epic Link field in the issue

After linking issues using both the issue linking and the epic link one can note the difference when view the Epic issue:

I hope it helps. If this answer helps solve the problem, please come back and mark this answer as solved to help other community members with the same challenge. If not, you are welcome to share your solution as well.

Cheers,

Alex

All comments

Alex_dddmmh

Hi @Tamas Salamon, and welcome to the community!

The linking between Epics and other standard issues (Stories, Bug, etc.) is established by the Epic Link field on the standard issue. Therefore you might use these two methods to get it working:

1 - Create issues from the Epic

Navigate to your Epic issue and hit Create Issue in Epic

2 - Edit the Epic Link field in the issue

After linking issues using both the issue linking and the epic link one can note the difference when view the Epic issue:

Cheers,

Alex

Trudy P Claspill

@Tamas Salamon

The short answer is no, your method does not work for Jira to consider the issue a "child" of the Epic.

You utilized the generic issue linking functionality. Why the labels used for these links may imply a parent/child relationship between the issues, that does not mean that Jira sees it as a parent/child relationship.

For Jira to recognize an issue as a child of an Epic, and apply its built-in functionality that applies to that relationship, the Epic Link field in the child issue is how the relationship is identified, as explained by @Alex

Tamas Salamon

Thanks Trudy, I was not specifically needing the parent / child link although in agile the epic to story implies a hierarchy

But I see that whereas the rest of the link type labels make sense i.e. "is blocked by" means the other ticket "blocks". The relationship is accurately described depending on which side of the linkage is viewed

But a link of "is a story of" shows as "is a bug of" on the other side only make sense if ticket 1 is a story and ticket 2 is a bug. If either are any other types like epic, task, etc. it does not make sense.

I will limit my use of this linking function then

Tamas Salamon

Hello Alex

Thanks for your comprehensive reply - appreciated.

I extracted a mapping of these link types:

Source Target

is blocked by blocks

blocks is blocked by

is story of is a bug of

is a bug of is story of

is cloned by clones

clones is cloned by

is duplicated by duplicates

duplicates is duplicated by

relates to relates to

So the story / bug link should only be used where you have a story and related bug. On other ticket types, this meaning may not make sense.

To make it clear, I would replace this pair with something like

issue having bug bug of issue

And when just want to link tickets to use "relates to"

Regards

John Funk

That is correct. You can create whatever link types you want - with whatever names you want. But they are always in the same type of relationship - you cannot get them to have a more controlled link like an Epic or a Sub-task does.

Tamas Salamon

Thanks John, I did not realise that the descriptions are configurable. Definitely will change them to make sense of the relationship.

Happy to note that a linkage is a reciprocal relationship rather than hierarchical and will view the two type of linkages as such

Trudy P Claspill

I see that John already explained that these issue links are configurable. The link "is story of/is bug of" is something that a Jira administrator added to your system. It is not a pre-defined link relationship defined automatically by Jira. You would have to get information from your Jira admin who created that link to determine what its purpose is.

In the places I've worked with Jira, we've actually used a Jira project to track stories for configuration changes to Jira itself, so that we would have some records to reference in cases like this.

Tamas Salamon

Thanks Judy, I was not aware that this was an admin configured description but thought this was something set by default. In this case, I have send the correct descriptions to jira admin to accurately reflect this relationship, in this pair.

Interesting to use jira project to hold config settings, may want to do this in the future as well.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud