Details
-
Story
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Done
-
None
-
Agile
-
BigPicture
-
JIRA server, JIRA cloud
-
12
-
-
Business
-
Sprint 2019/19, Sprint 2019/21
-
0.25
-
No
-
3 days, 1 hour, 31 minutes, 43 seconds -
3 days, 42 minutes, 58 seconds -
2 weeks, 1 day, 46 minutes, 48 seconds -
3 days, 2 hours, 49 minutes, 37 seconds -
0 -
0 -
3 days, 22 hours, 17 minutes, 30 seconds -
Description
As-is:
A system requires a configuration of scope synchronization for a Box backlog and all team Box backlogs.
To-be:
A system requires a configuration for at least one team involved in a Box. User can set a value of synchronized Box field as "--Not synchronized --". The option is available only when "Team specific" mode is selected.
In case a synchronization of team Box backlog or a Box backlog is set as "not synchronized", a system does not:
- update a Box backlog/ a team Box backlog after a synchronized field was updated in Jira (the same as it works in "No synchronization" mode)
- update a Box synchronized field after the scope of a Box was updated, e.g. some task was planned for an iteration (the same as it works in "No synchronization" mode).
Please note, that once "Sprint" field is selected as a Box field, a system always set "not synchronized" value until Jira board field is set.
A warning message for unconfigured Boxes in a Scope synchronization screen is different for a Team-specific mode after a change is applied. New message:
"Synchronization is not configured yet. Define field value for at least one team"
Attachments
Issue Links
- has to be done before
-
ONE-17462 Scope synchronization doesn't synchronize Unassigned tasks on Board 2.0
-
- Closed
-
- is child of
-
INITIATIVE-37 Board 2.0 is fully-fledged
-
- Closed
-