Public

agile_dashboard_template(4).xml

(110 kB)

(6 kB)

vardump.png

agile_dashboard_template.xml

(115 kB)

agile_dashboard_template(1).xml

(116 kB)

Screenshot from 2017-02-23 15-40-22.png

(132 kB)

Screenshot from 2017-02-23 15-37-55.png

(289 kB)

TrackersImportedSuccessfully.PNG

(61 kB)

Template sucessfully imported.PNG

(64 kB)

(57 kB)

Imported hierarchy.PNG

agile_dashboard_template(1).xml

(116 kB)

References

Cross references

Referencing request #9885

Git commit

tuleap/tuleap/stable

Merge commit 'refs/changes/56/7456/35' of ssh://gerrit.tuleap.net:29418/tuleap 46b785a150

Manuel Vacelet (vaceletm) , 2017-02-24 15:22

request #9885: Blank page when accessing to agile dashboard services bd34bcdc75

Seif Eddine Gamoudi (gamoudis) , 2017-02-24 14:23

Show items referenced by request #9885

Referenced by request #9885

Artifact Tracker v5

rel #9841 9.5

Other

gerrit #7456

Follow-ups

2017-02-24 15:25

The issue was with my dev environment. Sorry about that.

Patch integrated in Tuleap 9.4.99.136. Thanks for the contrib

Status changed from Under review to Closed
Connected artifacts
- Added Fixed in: rel #9841
Close date set to 2017-02-24

2017-02-24 11:29

Hi,

I can't reproduce the problem, here is the result of me importing the template you have provided

Attachments TrackersImportedSuccessfully.PNG, Template sucessfully imported.PNG, Imported hierarchy.PNG, agile_dashboard_template(1).xml added
By Seif Eddine Gamoudi (gamoudis)
(61 kB)
TrackersImportedSuccessfully.PNG
By Seif Eddine Gamoudi (gamoudis)
(64 kB)
Template sucessfully imported.PNG
By Seif Eddine Gamoudi (gamoudis)
(57 kB)
Imported hierarchy.PNG

2017-02-23 15:44

On project creation based on attached template I got a warning about a missing index

Then, when I go on AD page, I get the given fatal error

Attachments agile_dashboard_template(1).xml, Screenshot from 2017-02-23 15-40-22.png, Screenshot from 2017-02-23 15-37-55.png added
By Manuel Vacelet (vaceletm)
(132 kB)
Screenshot from 2017-02-23 15-40-22.png
By Manuel Vacelet (vaceletm)
(289 kB)
Screenshot from 2017-02-23 15-37-55.png

2017-02-21 11:38

I confirm it's the intended behaviour. The method should return a hierarchy, as the submitted tracker is not part of any hierarchy, it shouldn't return anything.

2017-02-21 11:14

last edited by: Seif Eddine Gamoudi (gamoudis)

2017-02-21 11:18

shouldn't the return of the method be at least the tracker it self if it has no hierarchy?
I just thought it s a little bit weird that s all, we could get past it if that s the intended behaviour.

2017-02-21 10:55

As tracker 11 is the Bug tracker and that bug is outside the hierarchy I don't think it's a bug that it's not returned

2017-02-21 09:17

Here it is :)

Attachments agile_dashboard_template.xml added

2017-02-21 09:06

It depends of the hierarchy I guess, could you attach an export of your AD structure ?

2017-02-20 15:46

last edited by: Seif Eddine Gamoudi (gamoudis)

2017-02-20 15:58

Hi, i think i hit a bug in the the method you proposed (Tracker_HierarchyFactory::getHierarchy()->flatten()).

i put in the attachment the vardump of the array passed as parameter aswell as the result of the proposed method.

Given the description of the method it should return at least all the values present in the parameter (tracker with id 11 is missing here).

Attachments vardump.png added
By Seif Eddine Gamoudi (gamoudis)
(6 kB)
vardump.png

2017-02-16 11:12

With patchset 26:

Both "Epic" and "User stories" are not "instantiated for new projects", when I create a project based on a template that was created with this XML:

User story gets created (good)
Epic is not created (error => as epic is parent of US, even if it's not en AD config it should be instantiated too).

Status changed from New to Under review
Assigned to changed from None to Seif Eddine Gamoudi (gamoudis)
Attachments agile_dashboard_template(4).xml added

2017-02-14 12:40

Thanks for the explanation!
Patchset waiting for review :)

2017-02-13 17:19

Today the management of template cloning at agile dashboard level is done in 2 phases:

it duplicates only the agile dashboard configuration (are scrum / kanban activated)
After TRACKER_EVENT_TRACKERS_DUPLICATED event, it duplicates planning related informations

This means that the AD creation is meant to be done as a post action of tracker duplication.

Hence, I propose that, in tracker, before the duplication of trackers, you emit an event to gather all trackers meant to be duplicated. The agiledashboard will identify all the backlog, planning & kanban trackers and.. that's it. The normal process should be smooth after that.

2017-02-13 16:50

By it s template am refering to the template of project A, making sure the trackers affiliated with agile dashboard are instantiated for new projects.
Concerning the implementation am not sure yet , would have to dive deeper into the code.

2017-02-13 16:28

The problem occurs when you try to create a project (A) from an already existing one (B).
As far as i understood when u try creating project A, the template of project B is going to be the template of project A.

Correct

Is it acceptable to check if project B contains trackers affiliated with agile dashboard and force it s template to contain those trackers?

What is "it's template" in this context, I'm not sure to understand.

+ how do you intend to "force" to contain those trackers ?

2017-02-13 15:58

Hi,

I do not intend to touch the default template.
The problem occurs when you try to create a project (A) from an already existing one (B).
As far as i understood when u try creating project A, the template of project B is going to be the template of project A.
What i want to know:
Is it acceptable to check if project B contains trackers affiliated with agile dashboard and force it s template to contain those trackers?

2017-02-13 15:31

Since my Understanding of the way things work is somewhat limited, I would appreciate if you would explain a bit how the template is created so i can force the template to contain The dependent trackers and that way ensure that the creation goes by smoothly

In tuleap, any project can be a template for another. This is done when you create a new new project, you can either:

Create from "Default Site Template"
or from any project you are administrator

But you can also, as site administrator, promote any project as a template. In site admin, look for a project and in "Type" dropdown list select "Template" (the default is "Project".

I suggest that, instead of modifying the default template, you create a new one with the trackers (hence you won't polluate your default template).

2017-02-13 09:20

Hi,

So Manuel suggested that i should add "an event at project creation to ensure dependent trackers are properly duplicated".
I pulled out the code and started tracking where the creation takes place and i found out that actually the project is created from a template that is referenced by its ID.
Since my Understanding of the way things work is somewhat limited, I would appreciate if you would explain a bit how the template is created so i can force the template to contain The dependent trackers and that way ensure that the creation goes by smoothly.

2017-02-01 12:29

Hi,

I have published a patch on gerrit https://gerrit.tuleap.net/#/c/7456/ In wich i disabled the checkboxes when a tracker is part of a scrum or kanban heirarchy.