We should expand on the open issue summary now on the site status report page with more detailed reporting - e.g., a report showing all issue groups across all migrations (so one spot to see which migrations have open client issues, which have open implementor issues, etc.).

Comments

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented

Another report I'd like to see - if issuePattern is set (the migration is using issue numbers linked to Trac or somesuch), report on all open issues (priority <> OK) without associated issue numbers, to help make sure every open issue is formally tracked.

moshe weitzman’s picture

moshe weitzman commented

Way in the future, I think could fetch issue status and assignedTo info from the target system using an API or scraper. Its not that hard and very useful.

moshe weitzman’s picture

moshe weitzman commented

It would be natural to use a sortable table with filters to present this data but we don't have database data here. We have a couple options

1. On every viewing of a report, just empty and populate a table and then build a drupal sortable table from it.
2. Use a jquery grid control to present the data such as http://wiki.github.com/mleibman/SlickGrid/examples. This adds an optional dependency.

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Component: migrate_ui (D7) » Code
Status: Active » Postponed (maintainer needs more info)

A couple of years later... In my experience, although the issue tracking seemed like a neat idea at the time, in practice we haven't really used it much in real-world projects. Is anyone out there using it? Any need for reporting capabilities here?

mikeryan’s picture

mikeryan
he/him
Primary language English
Location Pittsfield, MA, USA
commented
Status: Postponed (maintainer needs more info) » Closed (won't fix)