Unable to see the list of stories in an epic using structure

[Venkatraman]

We have 15+ component teams (lets call it N) and 30-40 releases running across them at any given point in time. The way JIRA has been structured is that EPIC = release and stories under the epic (Created using "Issues in Epic") link are the stories across the N teams. 1 or more stories per component team.

After installing the Struture plugin, I am unable to view the existing hierarchy across the various projects. Is there something I am missing ?

Will structure ONLY show up items created using structure ? Or how can one import the existing ones into the structure DB ?

[Igor Sereda [ALM Works]]

Hello Venkatraman,

Currently Structure is a kind of a swiss army knife - you can apply it to solve different problems, but it doesn't tell you how. (We'll be changing that in versions 3.0 and later.)

So off the shelf, Structure comes without any actual structures - you get a single "Global Structure" by default, which is empty and can be filled with issues, and you can create as many other structures as needed. The semantics of what it means for an issue to be in a structure and under some other issue is also left for the end-user to adopt.

There are basically two ways to define structures: manually and via synchronizers. Both methods can be used on a structure.

When structure is defined manually, you'd manually add one or more issues to a structure, arranging them in some order and hierarchy according to your needs. You can use "Search" feature to find the needed issues and add them in bulk, drag-and-drop to rearrange them, in-place issue creation to build a structure with some new issues, and in-place editing and JIRA actions to change the issues in the hierarchy.

With synchronizers, you can have Structure plugin do a mass-import for you (one-time synchronization a.k.a. Import or Resync), or you can install a synchronizer into a structure for continuous monitoring and updating of the structure and issues. In your case, you can add a Filter synchronizer that would add the issues to structure and GreenHopper synchronizer that would synchronize Epic-Story relationship in Agile board with the parent-child relationship in the structure.

Hope this helps a bit. You can read more about synchronization here: https://wiki.almworks.com/x/hQBg

For starters, I'd advise trying running Import with various parameters in one browser window, while monitoring the results on the Structure board in another window.

Kind regards,
Igor