Hi Claus, JIRA Portfolio is not significantly impacted by this: It is optimized and geared towards JIRA Software (in terms of terminology, and focus on planning tailored to software teams with concepts like epics, stories and sprints), but technically it also functions with JIRA Core and JIRA Service Desk as it relies on capabilities of the JIRA platform which all these products still have in common (such as JIRA projects, issues, JQL filters etc. ). When used with JIRA Core, Portfolio is expected to behave the same way as when previously using it with "plain" JIRA, without the JIRA Agile plugin. In this case, there are slight functional differences in the integration, because the "Epic" issue type does not exist out of the box, and some other details like retrieving velocity from a board are not available, but the rest works the same.
Please note that this answer refers to Portfolio 1.10.4 - we're working on a tighter integration with JIRA Software for future releases of Portfolio which might change compatibility
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.