Details
-
Epic
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Done
-
None
-
None
-
Business
-
Back structure builders
-
Tree
-
BigPicture, BigGantt
-
JIRA server, JIRA cloud
-
319
-
319
-
-
-
Sprint for Cadence 2018/27, Sprint for Cadence 2018/28, Sprint for Cadence 2018/32, Sprint 2019/13
-
PI2021/7
-
13
-
Yes
Description
Before change:
When user manually changes position of a task in hierarchy (indent/outdent/move) no changes occur in the task source (eg. Jira).
After change:
When user manually changes position of a task in hierarchy and the task falls under an active structure builder then the structure-building relation is reflected back in task source. This also covers cases where the task stops belonging to a structure builder of a given type as a result of action taken in the App.
Examples:
- When moving Jira task under an epic, the epic link is changed
- When moving Jira task under another task, with the parent-child link structure builder active, then the two tasks are connected with parent-child link
- When moving Jira task under sprint, it is reassigned to that sprint
NOTES:
Structure builders supported by the mechanism in the 8.4 release:
1. Project
2. Epic
3. Version
4. Sprint
5. Sub-task
6. All link-based structure builders
7. Jira (Advanced) Roadmaps - Parent Link
Structure builders to be supported in the 8.5 release:
1. Component
This change doesn't cover cases where the task stops belonging to a structure builder of a given type as a result of action taken in the task source - this is covered by ONE-27936
Attachments
Issue Links
- fixes
-
ONE-1530 Synchronization based on links' circular relationship causes tasks to switch places
-
- On hold
-
- has to be done before
-
ONE-27936 When a field corresponding to an active structure builder is left empty in a Jira issue, the task structure is adjusted accordingly.
-
- Waiting for Release
-
-
ONE-45614 When creating a Jira issue in BigPicture in the Gantt and Scope modules, relevant issue fields responsible for its position in the task structure (e.g. Epic link) are populated in accordance with active structure builders
-
- Waiting for Release
-
- is child of
-
INITIATIVE-98 Improved task structure management
-
- In Analysis
-
- is duplicated by
-
ONE-1614 I want fixVersion to be automatically associated to the issue once it is manually indented
-
- Closed
-
-
ONE-1885 As a user I would like to create epic links by drag&drop in Gantt
-
- Closed
-
- relates to
-
ONE-5859 Users without Jira Edit Issue permissions are able to indent/outdent tasks on Scope module
-
- Closed
-
-
ONE-7094 Validation of task position on WBS based on activated synchronizers
-
- Closed
-
-
ONE-37788 Improved behaviour of creating Jira issue as a subtask for basic task
-
- Closed
-
-
ONE-41148 Switch: Allow for manipulating manually the task structure on Scope / Gantt
-
- Closed
-
-
ONE-27936 When a field corresponding to an active structure builder is left empty in a Jira issue, the task structure is adjusted accordingly.
-
- Waiting for Release
-
- split to
-
ONE-40064 Manual changes of task position in task structure are reflected in task's structure building fields (e.g. Epic link) as per activated structure builders - support for 'Jira (Advanced) Roadmaps - Parent Link' structure builder
-
- Closed
-
-
ONE-40067 Manual changes of task position in task structure are reflected in task's structure building fields (e.g. Epic link) as per activated structure builders - support for Component structure builder
-
- Waiting for Release
-
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...