Protfolio vs. Structure plugins

[Erez Morabia]

Hi ,
We have Protfolio plugin, but the usage is low. People mainly use that for looking the hierarchy of the issues (Initiative/Feature/EPIC/Story) and their progress.
Recently we identified the need to have 2 levels of user stories - 'functional user story' and 'technical user story'. The reason behind that is that we have component teams. Therefore, each 'functional user story' should be implemented by a few 'technical user stories'.
Basic JIRA doesn’t have that. So someone referred me to 'structure' plugin. Structure seems to be up to the job.
My question is whether Portfolio and Structure plugins are contradicting each other? are they overlapping? should I recommend my organization to use only one of them?
Suppose I want Structure, any concerns you see by stopping using Portfolio?

Thanks,
Erez

[Egor Tasa [ALM Works] · Accepted solution]

Hi Erez,

Structure and Portfolio are compatible, and Structure even has integration with Portfolio, visualizing the Portfolio parent link. 

Portfolio and Structure share some of the functions, but mainly Portfolio is aimed at planning, while Structure at visualization and manipulation of the hierarchy.

There are many people out there using both apps in tandem.

If you have more questions about Structure, you can always contact support@almworks.com

Regards,
Egor Tasa

ALM Works