Allow issues to be targeted toward say v1.0 and v1.5 and v2.0 and at the same time allow each version be indepently pushed through the work flow that would result in each to potentially have different states and/or status'
Not possible OOTB. You could use sub-tasks as a workaround and have the parent item workflow have 'sub-tasks blocking condition'. Each sub-task will have the FixVersion as per the release (in your example 1.0 and 2.0)
Version hierarchy is for dependency between versions. But in your case you have one issue with corrections for multiple versions following it's own schedule. You can use GH with a main Epic and Stories for each of the versions linked to the Epic.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the reply....what about Green Hopper and using Version Hierarchy ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.