Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Do we have Time Tracking overall report/aggregate in Next Gen project (same as In Classic project)

Kwai Ling Ma
February 4, 2020

Do we have any Time tracking aggregate/report in Next gen project, as I see in Classic project report.

There are very few reports in Next Gen projects compared to Classic Project, unless I am missing something.

Other question is, can we create multiple boards in Next Gen project, Because some of my issues follow Sprint and some Kanban

Thank you

Regards

Kwai

 

 

 

3 answers

0 votes
DI2E Licensing
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 20, 2014

Here's a lot more data.

Further research on the links in DMO-460
* In Source, there are two links in the ticket, one is to TEST-1213 (also in destination) and one is to DIB-1765 (not in Destination)
* In Destination, there are also two links, TEST-1213 and MACE-1707.
* This history in both systems is identical. JoeBob created the link to DIB-1765 on 7/11 and Thomas created the link to TEST-1213 on 7/25.
* In destination DIB-1765, no links are shown, and yet there are two links in the history prior to the import. The history is identical to the source history, where the two links are shown.

A timeline

1445 - TEST-1213 imported
1524 - MACE-1707 imported
1711 - DIB-1765 imported
1727 - TEST-1213 was linked to DIB-1765 (this shows up in the history for TEST-1213 but not the history for DIB-1765) This is a link that should be appearing in both tickets and does not appear in either.
1828 - DMO-460 imported
1834 - TEST-1213 was linked to DMO-460. This appears in the TEST-1213 history, but not in the DMO-460 history. This appears correctly in both tickets.

There is no import history that shows the creation of the link between DMO-460 and MACE-1707. A link that should not be there but appears in both tickets.


There is no import history that shows the creation of the linke between MACE-1707 and TEST-1213. A link that should not be there bu appears in both tickets.

|| Ticket || No. of links in Source || No. of links in Destination ||
| DMO-460 | 2 | 2 |
| DIB-1765 | 2 | 0 |
| TEST-1213 | 2 | 2 |
| MACE-1707 | 4 | 6 |

So we have the correct number of links but they are misplaced.

Missing links:
* DMO-460 and DIB-1765
* TEST-1213 and DIB-1765

Added links:
* MACE-1707 and DMO-4690
* MACE-1707 and TEST-1213

It's as though MACE-1707 got the links that DIB-1765 should have had.

0 votes
Mehmet Kazgan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 19, 2014

You see anything weird in the logs?

DI2E Licensing
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 19, 2014

I imported 18 projects. The logs are pretty verbose. When I get a few minutes I'll see if there's anything that pops out. thx

0 votes
Mehmet Kazgan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 19, 2014

Did you do a full-index in the target instance after importing to the target instance? Usually that takes care of the issue you are having.

Mehmet

DI2E Licensing
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 19, 2014

Just tried that. No luck.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events