Productboard integration for Jira

Big minus is that if you break epics (from Productboard) down in JIRA, then as noted below, child tasks are not associated with the epic in Productboard when they are synced back to Productboard.

This feature is definitely a must-have for every organization that uses Productboard and Jira as tools to support their processes. However, some things can be improved, so I didn't review it with the four stars. * We cannot associate a field from Jira that is a date into Productboard because there is no Date type to use in custom fields in Productboard. * In case we are using other kinds of Jira's issue types (for instance, a higher issue type that aggregates several Epics), if we have it map to Productboard's features and Epics to subfeatures when we push a subfeature, it doesn't link it to the father issue. * There are no audit logging to when things change (description, header, a specific field). To be fair, this is not only related to the Jira integration part of the product. Other than that, the integration works really fine and in a very performant way.

This is a "must-have" for ProductBoard users. However (and this is why I'm giving a low rating), there are some conceptual issues that you must work around. Productboard Features = JIRA Epics Productboard Sub-features = JIRA Stories So far so good.. But if you auto-import from jira... your JIRA Stories are considered Productboard Features (i.e. epics!)

Works great. Sometimes, out of the blue, erases Jira description, still not sure why