-
Bug
-
Resolution: Fixed
-
Low
-
10.79
-
1
-
Severity 3 - Minor
-
Avengers - USH4
Issue Summary
User cannot select "unassigned backlog" as an option to save a capability when the field is set as mandatory
This behaviour is not consistent with other work items such as Features, and prevent users to save work on Capabilities (choosing "unassigned backlog as the intended selection
Steps to Reproduce
- In administration> details panel> set single Program Increment as mandatory field for Capability, for a program/portfolio
- Create or open a capability under the same program
- Try to save with PI set as "Unassigned backlog"
Repeat same operation for feature and notice the difference
Expected Results
When set to only single PI -selection for capabilities and epics, the system should let the user save Unassigned Backlog as an option.
Actual Results
The system forces the user to select a nominated PI
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JIRAALIGN-2113] [JIRAALIGN-2113] "Unassigned backlog" is not taken as an option in Capabilities when PI is set to mandatory
| Labels | Original: ja-bb ja-cs-fg | New: ja-bb ja-cs-fg repo-? |
| Labels | Original: ja-cs-fg | New: ja-bb ja-cs-fg |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Waiting for Release [ 12075 ] | New: Closed [ 6 ] |
| Sprint | New: Avengers - USH4 [ 6119 ] |
| Assignee | Original: Lesia Ferents [ f4ea3206508b ] | New: Iryna Dziadyk [ idziadyk@atlassian.com ] |
| Status | Original: In Review [ 10051 ] | New: Waiting for Release [ 12075 ] |
| Fix Version/s | New: 10.84 [ 93022 ] |
| Description |
Original:
h3. Issue Summary
User cannot select "unassigned backlog" as an option to save a capability when the field is set as mandatory This behaviour is not consistent with other work items such as Features, and prevent users to save work on Capabilities (choosing "unassigned backlog as the intended selection h3. Steps to Reproduce # In administration> details panel> set *single* Program Increment as mandatory field for Capability, for a program/portfolio # Create or open a capability under the same program # Try to save with PI set as "Unassigned backlog" Repeat same operation for feature and notice the difference !image-2020-09-28-16-58-35-197.png! !image-2020-09-28-16-58-27-646.png! h3. Expected Results When set to only single PI -selection for capabilities and epics, the system should let the user save Unassigned Backlog as an option. h3. Actual Results The system forces the user to select a nominated PI h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
User cannot select "unassigned backlog" as an option to save a capability when the field is set as mandatory This behaviour is not consistent with other work items such as Features, and prevent users to save work on Capabilities (choosing "unassigned backlog as the intended selection h3. Steps to Reproduce # In administration> details panel> set *single* Program Increment as mandatory field for Capability, for a program/portfolio # Create or open a capability under the same program # Try to save with PI set as "Unassigned backlog" Repeat same operation for feature and notice the difference !image-2020-09-28-16-58-35-197.png! !image-2020-09-28-16-58-27-646.png! h3. Expected Results When set to only single PI -selection for capabilities and epics, the system should let the user save Unassigned Backlog as an option. h3. Actual Results The system forces the user to select a nominated PI h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
| Assignee | Original: Bohdan Bondarets [ bbondarets@atlassian.com ] | New: Lesia Ferents [ f4ea3206508b ] |
| Status | Original: In Progress [ 3 ] | New: In Review [ 10051 ] |