-
Suggestion
-
Resolution: Fixed
Check discussion on AAC
https://answers.atlassian.com/questions/104490/how-to-assign-an-issue-to-a-greenhopper-sprint/104867
When you are looking at an issue (not in the context of the planning board), you should be able to indicate in what sprint you want this issue to be done. This is typical when you encounter the issue while triaging, and you know that you are going to address similar issues in a future sprint.
Also related to GHS-4949
[JSWSERVER-6569] As a user, I want to assign an issue to a specific sprint, (like I can assign it to a fix version), such that the issue is planned
Workflow | Original: JAC Suggestion Workflow [ 3065253 ] | New: JAC Suggestion Workflow 3 [ 3655717 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2622566 ] | New: JAC Suggestion Workflow [ 3065253 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2321787 ] | New: Confluence Workflow - Public Facing v4 [ 2622566 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 [ 2041124 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2321787 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2030127 ] | New: JIRA PM Feature Request Workflow v2 [ 2041124 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 [ 737029 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2030127 ] |
Labels | Original: triaged | New: affects-server triaged |
Workflow | Original: GreenHopper Kanban Workflow v2 [ 447327 ] | New: JIRA PM Feature Request Workflow v2 [ 737029 ] |
Issue Type | Original: Story [ 16 ] | New: Suggestion [ 10000 ] |
Priority | Original: Major [ 3 ] | |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Fix Version/s | New: 6.3.9 [ 38696 ] | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Link | Original: This issue relates to JAGDEV-525 [ JAGDEV-525 ] |