|
An alternative way to solve this problem is surely to enable filters to match all Jiras in a specified set of project/release pairs. That way, if a given production turnover will include the disting of project A, release x, and project B, release y, it would be simple to create a filter (and thus a report) that lets one track during the development cycle all relevant issues.
In my case, we use 'projects' on a per-customer basis. Therefore, each version release will have items for different customers and general bugfixes - creating, managing versions across all the projects is very time-consuming. A "global version" vs "project-specific version" methodology would be desirable for us.
As an ISV type of company we have to create/maintain our main product's version across almost all projects ==> this feature would be helpful and simplify administration.
This would help us as well. I am at a company that does hosted (Software as a Service) apps. Our process works like this:
We would also like to have this feature implemented.
We use an "external open" project for the communication with our customers and an internal one to keep the internal "techie-talk" and the technical details apart from the customer. Till now there's no possibility to include the issues from both (or several) projects within one version for planning and management. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Major
Create versions on multiple projects
This is considered critical for the managers in my company.