-
Suggestion
-
Resolution: Won't Do
-
None
-
None
-
None
-
1
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Current Behaviour
Release version and view is associated with only one project.
Example Scenario
We are using JIRA to support multiple customers that are using our same product, some of those customers are using the same product version, and therefore are tied to a release cycle for that product version. Under the current implementation I am mapping customer issues to our product release on a JIRA project by project basis. This is fine for a customer-facing view. But there are scenarios where I have implemented a couple JIRA projects for 1 customer to accommodate their workflow. In this 2nd scenario looking at a release on a JIRA project by project basis fails.
Requested Behaviour
Allow to view multiple release version under one release view page. We can have this in board's release menu. Customer could define a product version, and under that have various releases versions. Then in any of the JIRA projects they would just tie the project to that product version(s), and thereafter be able to select fix version(s) from the list of releases that exist under that product version.
- relates to
-
- Closed
[JRASERVER-62015] Release view that span multiple JIRA projects
| Workflow | Original: JAC Suggestion Workflow [ 3055057 ] | New: JAC Suggestion Workflow 3 [ 3693220 ] |
| Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
| Resolution | New: Won't Do [ 10000 ] | |
| Status | Original: Gathering Interest [ 11772 ] | New: Resolved [ 5 ] |
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2619685 ] | New: JAC Suggestion Workflow [ 3055057 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2593482 ] | New: Confluence Workflow - Public Facing v4 [ 2619685 ] |
| Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2351267 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2593482 ] |
| Support reference count | New: 1 |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2127314 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2351267 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2089980 ] | New: JIRA Bug Workflow w Kanban v6 [ 2127314 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 1583345 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2089980 ] |
| Description |
Original:
*Current Behaviour*
Release version and view is associated with only one project. *Example Scenario* We are using JIRA to support multiple customers that are using our same product, some of those customers are using the same product version, and therefore are tied to a release cycle for that product version. Under the current implementation I am mapping customer issues to our product release on a JIRA project by project basis. This is fine for a customer-facing view. But there are scenarios where I have implemented a couple JIRA projects for 1 customer to accommodate their workflow. In this 2nd scenario looking at a release on a JIRA project by project basis fails. *Requested Behaviour* Allow to view multiple release version under one release view page. We can have this in board's release menu. Customer could define a product version, and under that have various releases versions. Then in any of the JIRA projects they would just tie the project to that product version(s), and thereafter be able to select fix version(s) from the list of releases that exist under that product version. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-62015]. {panel} *Current Behaviour* Release version and view is associated with only one project. *Example Scenario* We are using JIRA to support multiple customers that are using our same product, some of those customers are using the same product version, and therefore are tied to a release cycle for that product version. Under the current implementation I am mapping customer issues to our product release on a JIRA project by project basis. This is fine for a customer-facing view. But there are scenarios where I have implemented a couple JIRA projects for 1 customer to accommodate their workflow. In this 2nd scenario looking at a release on a JIRA project by project basis fails. *Requested Behaviour* Allow to view multiple release version under one release view page. We can have this in board's release menu. Customer could define a product version, and under that have various releases versions. Then in any of the JIRA projects they would just tie the project to that product version(s), and thereafter be able to select fix version(s) from the list of releases that exist under that product version. |