Ok, a little background. So the company I work for has SIGNIFICANTLY hamstrung the use of Jira. They have eliminated the enhancement and feature issue types among many others to the point where we only have epics, stories, bugs, and subtask issue types available to us.
Problem: we have a new "nextgen" system being worked on and there are about five scrum teams working on it separately. Each team has their own series of epics for their work, so one single epic can not be created and used for this purpose. Because they have removed the feature issue type from use (which would have been useful here since epics roll up to features), they can not get a burndown based on the work they are collectively doing separated by team so instead they have all created their own fix/version release and are using the release burndown to track their work instead.
As the release manager, it is my duty to track, record, maintain, and otherwise ensure that our release procedures and other assorted quality control methods are sorted out so we don't get compromised in an audit situation. What this has done is now I have tickets appearing in multiple release fix/versions where there has (or will have) only one deployment. Policy currently states that any jira ticket that is in multiple fix/versions means that that particular jira ticket has been deployed twice. Now, if we were to be audited, it would obviously get rather confusing to prove when and where a ticket was ACTUALLY deployed.
There has to be another way to track multi-team, multi-epic burndowns. Please someone help me.