Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
I have this data from AzureDevOps(VSTS)- having the relationship as: Release>Epic>Feature.
I am using Gantt Chart by MAQSoftware custom visual.
Even though for GT-Release1 the Start and End date is 01-01-19 to 28-02-19 in the Gantt chart it shows the Start data from 01-01-19 to 31-03-2019. Any idea?
ReleaseID | ReleaseTitle | ReleaseStartDate | ReleaseTargetDate | EpicID | EpicTitle | FeatureTitle | EpicStartDate | EpicTargetDate | FeatureID | FeatureStartDate | FeatureTargetdate |
42368 | GT-Release1 | 01-01-19 0:00 | 28-02-19 0:00 | 42369 | GT-Epic1 | GT-Feature1 | 01-01-19 0:00 | 31-01-19 0:00 | 42379 | 01-01-19 0:00 | 15-01-19 0:00 |
42368 | GT-Release1 | 01-01-19 0:00 | 28-02-19 0:00 | 42369 | GT-Epic1 | GT-Feature2 | 01-01-19 0:00 | 31-01-19 0:00 | 42380 | 16-01-19 0:00 | 31-01-19 0:00 |
42368 | GT-Release1 | 01-01-19 0:00 | 28-02-19 0:00 | 42374 | GT_Epic2 | GT-Feature3 | 01-02-19 0:00 | 28-02-19 0:00 | 42383 | 01-02-19 0:00 | 28-02-19 0:00 |
42368 | GT-Release1 | 01-01-19 0:00 | 28-02-19 0:00 | 42377 | GT-Epic3 | GT-Feature4 | 15-02-19 0:00 | 31-03-19 0:00 | 42386 | 15-02-19 0:00 | 31-03-19 0:00 |
42373 | GT_Release2 | 01-03-19 0:00 | 30-04-19 0:00 | 42389 | GT-Epic4 | GT-Feature5 | 01-03-19 0:00 | 31-03-19 0:00 | 42390 | 01-03-19 0:00 | 31-03-19 0:00 |
42373 | GT_Release2 | 01-03-19 0:00 | 30-04-19 0:00 | 42393 | GT-Epic5 | GT-Feature6 | 15-04-19 0:00 | 15-05-19 0:00 | 42394 | 15-04-19 0:00 | 15-05-19 0:00 |
42375 | GT-Release3 | 01-05-19 0:00 | 30-06-19 0:00 | 42397 | GT-Epic6 | GT-Feature7 | 01-05-19 0:00 | 30-06-19 0:00 | 42398 | 01-05-19 0:00 | 30-06-19 0:00 |
42401 | OC-Release1 | 01-01-19 0:00 | 28-02-19 0:00 | 42403 | OC-Epic1 | OC-Feature1 | 01-01-19 0:00 | 31-01-19 0:00 | 42407 | 01-01-19 0:00 | 31-01-19 0:00 |
42401 | OC-Release1 | 01-01-19 0:00 | 28-02-19 0:00 | 42413 | OC-Epic2 | OC-Feature2 | 01-02-19 0:00 | 15-03-19 0:00 | 42414 | 01-02-19 0:00 | 15-03-19 0:00 |
42417 | OC-Release2 | 01-03-19 0:00 | 30-04-19 0:00 | 42419 | OC-Epic3 | OC-Feature3 | 01-03-19 0:00 | 31-03-19 0:00 | 42422 | 01-03-19 0:00 | 31-03-19 0:00 |
42417 | OC-Release2 | 01-03-19 0:00 | 30-04-19 0:00 | 42427 | OC-EPic4 | Oc-Feature4 | 01-04-19 0:00 | 31-05-19 0:00 | 42428 | 01-04-19 0:00 | 31-05-19 0:00 |
42431 | Oc-Release3 | 01-05-19 0:00 | 30-06-19 0:00 | 42432 | OC-Epic5 | OC-Feature5 | 01-05-19 0:00 | 30-06-19 0:00 | 42433 | 01-05-19 0:00 | 30-06-19 0:00 |
If I have some Epics that is spread across multiple product Releases, then how should I represent that?
Any idea or help would be really appreciated.
Hi @sprasad ,
The dates are good. Please refer to the snapshot below.
Does it mean an Epics has many releases? Maybe you should consider the Epics as the parent task. Please also try the Gantt Chart released by MS.
Best Regards,
Dale,
Release is a parent item and then Epic as child and then Feature as the sub child.
Let us take this scenarion: From the table Release ID - 42368 is spanning from 01-01-19 TO 28-02-19, but one of the Feature (4) in row4 is spanning from 15-02-19 TO 31-03-19. Now in the Gantt chart the Release dates gets extended as 01-01-19 TO 31-03-19, I am expecting that the Release will maintain its original duration i.e from 01-01-19 TO 28-02-19
I also tried the Gantt Chart from Microsoft, but the problem there is it shows the bars only for last child items which is Feature in my case. It should show the bars for Release and Epic as wel.
Regards
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
114 | |
99 | |
83 | |
70 | |
60 |
User | Count |
---|---|
150 | |
115 | |
104 | |
89 | |
65 |