• Type: Sub-task
• Resolution: Done
• Fix Version/s: None
• Affects Version/s: None
• Component/s: Timeline (Simple) - Issue List
• Labels:

  None

[JSWCLOUD-17590] In the new Next-gen project type, changing Epics order should "adjust" to their new position

Albert Kavelar made changes - 18/Aug/2020 3:57 AM

Remote Link

Original: This issue links to "Page (Confluence)" [ 466601 ]

Emily Chan (Inactive) made changes - 09/Jun/2020 3:01 AM

Description

Original: When changing the order of the epics in a next-gen project's roadmap, it would be great if the set dates to change too, depending to each other. Example:   Epic 1 - 1.2.2019 - 28.2.2019 Epic 2 - 1.3.2019 - 31.3.2019 Epic 3 - 1.4.2019 - 30.4.2019 If I change Epic 3 to position 2 in the roadmap and would like the dates to change: Epic 1 - 1.2.2019 - 28.2.2019 Epic 3 - 1.3.2019 - 31.3.2019 Epic 2 - 1.4.2019 - 30.4.2019

New: {panel:title=Atlassian status as of June 2020|borderStyle=solid|borderColor=#b2d4ff|titleBGColor=#b2d4ff|bgColor=#eaf1fc} Hello all, We have recently introduced the epic panel in next gen projects! With this capability, you can order your epics by dragging and dropping epics around in the panel. The same order will be reflected in your roadmap and board. To learn more and/or provide feedback about the epic panel, read [our community post here.|https://community.atlassian.com/t5/Next-gen-articles/Improved-Backlog-planning-in-next-gen-with-the-epic-panel/ba-p/1387675] We are closing this ticket. If you feel that this issue hasn't been fully addressed, please let us know! Thank you,  Emily Chan  Product Manager, Atlassian. {panel} When changing the order of the epics in a next-gen project's roadmap, it would be great if the set dates to change too, depending to each other. Example: Epic 1 - 1.2.2019 - 28.2.2019  Epic 2 - 1.3.2019 - 31.3.2019  Epic 3 - 1.4.2019 - 30.4.2019 If I change Epic 3 to position 2 in the roadmap and would like the dates to change: Epic 1 - 1.2.2019 - 28.2.2019  Epic 3 - 1.3.2019 - 31.3.2019  Epic 2 - 1.4.2019 - 30.4.2019

Emily Chan (Inactive) made changes - 09/Jun/2020 2:59 AM

Resolution		New: Done [ 17 ]
Status	Original: Open [ 1 ]	New: Closed [ 6 ]

Emily Chan (Inactive) made changes - 09/Jun/2020 2:58 AM

Assignee

New: Emily Chan [ echan@atlassian.com ]

Emily Chan (Inactive) made changes - 04/Jun/2020 12:03 PM

Remote Link

New: This issue links to "Page (Confluence)" [ 487267 ]

Erika Sa (Inactive) made changes - 10/Jan/2020 5:30 PM

Remote Link

New: This issue links to "Page (Confluence)" [ 466601 ]

Erika Sa (Inactive) made changes - 10/Jan/2020 5:13 PM

Component/s

New: Roadmap [ 53392 ]

Heitor T (Inactive) made changes - 29/Aug/2019 9:58 PM

Link

New: This issue is duplicated by JSWCLOUD-18296 [ JSWCLOUD-18296 ]

Monique Khairuliana (Inactive) made changes - 29/Aug/2019 12:50 AM

Workflow

Original: GreenHopper Kanban Workflow 20141014 - Restricted [ 3098144 ]

New: JAC Sub-task Workflow [ 3472418 ]

Gabriele Franck made changes - 11/Feb/2019 5:15 PM

Parent		New: JSWCLOUD-17392 [ 1094115 ]
Workflow	Original: JIRA PM Feature Request Workflow v2 - TEMP [ 3098143 ]	New: GreenHopper Kanban Workflow 20141014 - Restricted [ 3098144 ]
Issue Type	Original: Suggestion [ 10000 ]	New: Sub-task [ 6 ]

Gabriele Franck created issue - 11/Feb/2019 5:12 PM