Overview
When upgrading from Minyaa 3.x to Minyaa 4.x, the stored predefined reports will always be stored, but if theses reports are concerned by some evolution in their parameters, their conversion will be not covered by the Minyaa Report plugins.
Sadly, Minyaa Reports is not able to know how to convert them. Its behavior is more like your favorites/shortcut to a site/request in your browser ... When creating them, you may experience some change with future evolution of this site.
How to process ?
The more efficient way is to re-capture the same reports in the new version, and then update your previous predefined reports.
Reports from Minyaa plugins
You will find below some of change to perform for Reports provided by Minyaa Plugins.
Between Minyaa 3.x and Minyaa 4.x, the only change performed are related the Report Key, based on plugin Key.
| Plugin | ||
|---|---|---|
| Minyaa Time | jira.plugin.minyaa.time | fr.alkaes.minyaa.jira-plugin-minyaa-time |
| Minyaa Workflows | jira.plugin.minyaa.workflows | fr.alkaes.minyaa.jira-plugin-minyaa-workflows |
The update can be done without stopping JIRA, since no cache are managed for Predefined Report Definitions.
-- For Minyaa Time UPDATE reportentity SET REPORT_KEY='fr.alkaes.minyaa.jira-plugin-minyaa-time:workload-IssueType' WHERE REPORT_KEY='jira.plugin.minyaa.time:workload-IssueType'; UPDATE reportentity SET REPORT_KEY='fr.alkaes.minyaa.jira-plugin-minyaa-time:workload-project' WHERE REPORT_KEY='jira.plugin.minyaa.time:workload-project'; UPDATE reportentity SET REPORT_KEY='fr.alkaes.minyaa.jira-plugin-minyaa-time:workloadOnPeriod' WHERE REPORT_KEY='jira.plugin.minyaa.time:workloadOnPeriod'; UPDATE reportentity SET REPORT_KEY='fr.alkaes.minyaa.jira-plugin-minyaa-time:workload-issue' WHERE REPORT_KEY='jira.plugin.minyaa.time:workload-issue'; UPDATE reportentity SET REPORT_KEY='fr.alkaes.minyaa.jira-plugin-minyaa-time:workload-WorklogType' WHERE REPORT_KEY='jira.plugin.minyaa.time:workload-WorklogType'; -- For Minyaa Workflows UPDATE reportentity SET REPORT_KEY='fr.alkaes.minyaa.jira-plugin-minyaa-workflows:stats-transitions' WHERE REPORT_KEY='jira.plugin.minyaa.workflows:stats-transitions';
Other Reports
If you have used Minya Reports for Report from others Plugins, you will have to identify by yourself the needed changes.
Do not hesitate to share them !
-- Sample for Created vs Resolved report UPDATE reportentity SET REPORT_KEY='com.atlassian.jira.jira-core-reports-plugin:createdvsresolved-report' WHERE REPORT_KEY='com.atlassian.jira.plugin.system.reports:createdvsresolved-report';