You mean the "Open" event ? Confirmed.
I would suggest to not display it in the issue view anyway..
The double creation is probably caused by the table class... who's first ? ;)

The double creation is probably caused by the table class... who's first ? ;)

Yes it is. We should decide how to fix it:

1. Remove store action from the IssueModel;
2. Remove post actions from the IssueTable;

I am voting for second option, because IssueTable class should handle only methods which are related to the issues table. Any post actions are ugly, leave them to IssueModel.

@elkuku @mbabker your votes?

My vote goes to
1.a Comment out the store action in the model for now to fix this annoying bug and put a @todo on it.

Then think about a more general solution to implement 2 on the long run.

I played with a method in the hooks base controller addActivityEvent that accepts the needed parameters for an "event" in its parameters.
Maybe we can put something like this into a model and access it from within the other models ?

If you would like to implement it right away, and @mbabker has no objections, then, of course, go for it ;)

Currently too many issues we have. Agree to comment it out under todo.

So I just reimported the full joomla/jissues tracker on the site re-installing to get the milestone data in, the get project command is still inserting 2 open events.
You may blame the J!Tracker Application for transmitting this comment.

Yeap, you need to comment out Activity creation in the Get Issues and mark it as @todo.

True... go for it @b2z , while you're at it: The close action should also be commented out, as it currently also generates two close events..

Just pushed the commit to fix two open events.
@elkuku interesting, but I do not see in the IssuesTable any code related with the close event. How they can be doubled?

No that's a different beast... Currently this piece of code generates a "close" event - but since the "actor" is missing here, it's anonymous :(
So, only the get events CLI task is able to generate a proper "close" event - or a hook ;)
We have to really think this through how we handle those events...

So if it will be commented out everything will work fine?