-
Suggestion
-
Resolution: Low Engagement
-
None
-
0
-
1
-
Problem Definition
At the moment, Portfolio documentation on Releases does not exactly specify that Portfolio for JIRA can only consider one release/version associated with an issue.
Suggested Solution
It would be great to specify it in the documentation, to set the right expectation on the behavior for Portfolio (which is different than how JIRA treats version's associated with an issue)
- links to
[JSWSERVER-25279] Documentation improvement on Releases
Resolution | New: Low Engagement [ 10300 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
Labels | Original: API ril | New: API cleanup-seos-fy25 ril |
Labels | Original: API | New: API ril |
Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 979768 ] |
Component/s | Original: Documentation [ 36490 ] | |
Component/s | New: (Advanced Roadmaps) API / Documentation [ 73718 ] | |
Key |
Original:
|
New:
|
Project | Original: Advanced Roadmaps [ 16510 ] | New: Jira Software Server and Data Center [ 12200 ] |
Labels | New: API |
UIS | Original: 2 | New: 0 |
Workflow | Original: JAC Suggestion Workflow [ 3345530 ] | New: JAC Suggestion Workflow 3 [ 3666385 ] |
Workflow | Original: JPOSERVER JPOCLOUD Suggestion Workflow [ 3159335 ] | New: JAC Suggestion Workflow [ 3345530 ] |
Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2506914 ] | New: JPOSERVER JPOCLOUD Suggestion Workflow [ 3159335 ] |