version workload report

[Philip Winston]

We have two main projects, one for shared parts of the system and one for our first Application. Call the projects Shared and FirstApp. There will be future Applications. In both projects we've setup the same upcoming version, FirstApp-1.0. Because of course both the Shared and FirstApp projects will have issues related to the FirstApp-1.0 release.

We can create a JQL filter which views all open issues in both Shared and FirstApp for a specific version, so that's good.

But the Version Workload Report however seems to be for a single project only. It would be nice to run the Version Workload Report against the filter we have setup, which looks at both projects. Is this possible?

[ConradR · Accepted solution]

No. When you add the same Version name to two projects, you end up with two different versions.

btw: Having the same version in two projects doesn't seem right. You should consider using just one project with the components "Shared" and "FirstApp". (if this makes sense your project situation)

[Philip Winston]

You can construct a filter (JQL) wich lists all issues in version X in either project. That is, JQL does just a text match on the version name, it doesn't matter if the versions different or not, as long as they are named the same. So if the Version Workload Report took a filter (like most of the reports do) it seems like all would be well.

But yes I do wonder if we should be using one project and components. That would solve the Version Workload Report but it seems like it would create other problems. At a minimum then the component field is not fully available for other purposes. And the version field would need to have a union of all products being run out of that JIRA project. I dunno, is that what people do when they have shared code plus different applications built from that code, they run it all from one jira project?