Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Structure: how to Epic Link or Parent Link to include extend structures

I plan to use generators to select a certain set of Stories.  In the structure, I want to extend with either the Epic Links or the parent epic so that I can navigator to the parent epic and also go down to backlog items and tasks belonging to the stories.  

I can't figure out what extender to use to do that.

1 answer

2 votes

Hi Sam,

Dmitrii with ALM Works here.

Have you tried using the type of extend generator described in this article?

Hope this is what you were looking for, but feel free to contact us at We'll be able to take a closer look at your setup.

Kind regards,

Dmitrii Kuzmin

ALM Works

Hi Dmitrii,

thanks for your quick response.

I did look at the article and wasn't sure whether we have this "Advance Roadmap", if we do we don't use it.

We have the "Epic Link" with a story type and thought that may be a standard jira field.  Is it not?

If it is some sort of custom field, is it possible for me to define some action to use the custom field as a way to define the parent Epic?

Like Dave Rosenlund _Tempo_ likes this

The extender from the article will help in case you're using "Parent Link" field of Advanced Roadmaps to connect your Epics and Stories. 

In case of "Epic Link" you'll need this type of extender. 

Kind regards,

Dmitrii Kuzmin

ALM Works

Like Dave Rosenlund _Tempo_ likes this

It seems this is based on inserting based on Epics selection, and then expand the stories underneath the epic.

I want to use a selection criteria on certain attributes of stories, from the story then climb the hierarchy and include the epic in the epic link. 

Like Dave Rosenlund _Tempo_ likes this

I think it might be better for everyone involved if you contact the Structure support team directly, @Sam, so we can learn more about the specifics of your use case(s).  Then you can get the advice that's tailored to your needs (and we can post a summary of the resolution here for you and others to refer to it).

Please refer to this thread on the Atlassian Community when you do.



Suggest an answer

Log in or Sign up to answer

Atlassian Community Events